Trouble with LFE installs

[mikel evins]

I've been having trouble getting recent versions of LFE to work on both OS X and Ubuntu Wily. I know that the obvious next thing to ask is exactly what I;ve tried and exactly what went wrong, but that's a little hard to answer, because I've tried various things and seen various errors.

Just before posting, so that I'd have a concrete answer for that sort of question, I tried brew install lfe on my imac running OS X 10.11.4. Yes, I did brew update first, and brew doctor tells me everything is fine. Installing lfe works fine. Using the commands suggested by the page at https://github.com/lfex/lfetool appears to work fine. But running lfetool new service hello yields the following:

======================== EUnit ========================

unit-hello-tests: code-change-test ...[failed]

in function 'unit-hello-tests':'code-change-test'/0

**error:{assertEqual,[{module,'unit-hello-tests'},

              {line,11},

              {expression,"(: hello-server code-change (quote (111 108 100 32 118 101 114 115 105 111 110)) (quote (115 116 97 116 101)) (quote (101 120 116 114 97)))"},

              {expected,{ok,"data"}},

              {value,{ok,"state"}}]}

  output:<<"">>

=======================================================

  Failed: 1.  Skipped: 0.  Passed: 0.

make: *** [check-unit-only] Error 1

Is this expected?

I've also tried installing using apt-get on my Ubuntu Wily server, and seem different errors; I've tried building from source. I;ve tried closely following a couple of different getting-started documents. No joy.

Perhaps I'm doing something wrong. I don't know, and I don't really care; I'd be happy for any boneheaded mistake I'm making to be corrected. I just want a working installation of LFE on my Ubuntu server that I can use to build some apps with yaws, and I'm sort of lost in possibilities at the moment. I wouldn't even mind if someone told me I need to fetch everything by hand and build it from source, as long as doing that produced something I can actually use. I would just rather not expend more time than absolutely necessary doing an exhaustive search of all possible ways of getting stuff built and working.

Thanks in advance for any advice.

[Eric Bailey]

Sorry to hear you're having such a bad time. Any chance you could join Slack and @yurrriq? Maybe I can help. I've got OS X and Ubuntu (via xhyve) running locally.

https://lfe-slack.herokuapp.com/

Eric

--
You received this message because you are subscribed to the Google Groups "Lisp Flavoured Erlang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lisp-flavoured-e...@googlegroups.com.
To post to this group, send email to lisp-flavo...@googlegroups.com.
Visit this group at https://groups.google.com/group/lisp-flavoured-erlang.
For more options, visit https://groups.google.com/d/optout.

[Robert Virding]

A quick question. Have you tried downloading it directly from github:

https://github.com/rvirding/lfe

and then doing `make`

Robert

[Mason Staugler]

It looks like an error with a generated unit test for that project ("state" instead of "data). I think it's just a minor bug in lfetool.

Your LFE installation is fine; you can probably just crack open that test and fix it.

[Duncan McGreggor]

That's actually an intentional "bug" -- both the "library" and "service" projects generated by lfetool create a single unit test that you need to correct in order for your unit tests to pass. This is a hold-over from the days when it was really hard to get people to start doing TDD -- the theory being that by generating a test that users need to fix immediately, the users become aware of how unit tests work in LFE (we are more likely to use something when we know how it works).

Note, however, that lfetool is being phased out in favor of rebar3 LFE plugins (with a potential wrapper for those becoming the next revision of lfetool, probably named simply "ltool").

[Mason Staugler]

I didn't mean anything by "bug". All I write are bugs, so I think they're great. 😏

[Duncan McGreggor]

Hehehe :-)