py/deps/clj/src/clj-seq.lfe:6: error expanding (generate-predicate-wrappers)

[seanjensengrey]

▶ make
Getting dependencies ...
==> lfe (get-deps)
==> ltest (get-deps)
==> lutil (get-deps)
==> kla (get-deps)
==> erlport (get-deps)
==> clj (get-deps)
==> lcfg (get-deps)
==> goldrush (get-deps)
==> lager (get-deps)
==> logjam (get-deps)
==> py (get-deps)
Cleaning ebin dir ...
Compiling project code and dependencies ...
==> lfe (compile)
==> ltest (compile)
==> lutil (compile)
==> kla (compile)
==> erlport (compile)
==> clj (compile)
/Volumes/lake0/seanj/w/py/deps/clj/src/clj-seq.lfe:6: error expanding (generate-predicate-wrappers)
Compiling /Volumes/lake0/seanj/w/py/deps/clj/src/clj-seq.lfe failed:
ERROR: compile failed while processing /Volumes/lake0/seanj/w/py/deps/clj: rebar_abort
make: *** [proj-compile] Error 1

[seanjensengrey]

It looks like clj transmogrified itself. Looking at using an early version.

[seanjensengrey]

clj uses an lfetool with version 1.5.0-dev

seanj ~/w/py/deps/clj ▶ ./bin/lfetool -v
1.5.0-dev

While lfex/py uses

seanj ~/w/py ▶ ./bin/lfetool -v
1.4.0

[seanjensengrey]

I have had some success by using the specific lfetool that each dep downloads via make get-lfetool

make get-deps
for dir in `ls deps`; do ( cd deps/$dir; make get-lfetool ) done
find . -name lfetool

shows the following lfetools have been downloaded

./bin/lfetool
./deps/clj/bin/lfetool
./deps/kla/bin/lfetool
./deps/lcfg/bin/lfetool
./deps/logjam/bin/lfetool
./deps/ltest/bin/lfetool
./deps/lutil/bin/lfetool

With the following versions, find . -name lfetool -exec {} -v \;

1.4.0
1.5.0-dev
1.0.1
1.5.0-dev
1.5.0-dev
1.4.0
1.4.0

Compiling all the dependencies before hand prevented the earlier errors I saw.

for dir in `ls deps`; do ( cd deps/$dir; make compile ) done

[oubiwann]

Yikes! I never saw these comments!

• [x] 1. I'm currently going through py and lsci, trying to get things running again using the old rebar.
• [x] 2. Once this is done, I'll do a release, and then
• [ ] 3. migrate both to rebar3.

Most of the issues you have encountered should go away with rebra3 ... with the latest LFE release and rebar3, lfetool is not really needed anymore (lfetool was developed several years ago in response to the lack of tooling available to LFE projects, and that has since changed).

I'll update this ticket with progress.

[seanjensengrey]

No problem. I find github issues are kinda async-async ;)