Announcing Dryverl: an Erlang-to-C binding compiler

Richard A. O'Keefe <>
Tue May 30 06:50:19 CEST 2006


I downloaded dryverl-0.1 from the ObjectWeb site.
gzcat ...tar.gz | tar xvf -
cd dryverl-0.1
./configure --prefix=/users/local
make
...
make[1]: \
    Entering directory `/home/users/okeefe_r/erlang.d/dryverl-0.1/examples'
/home/users/okeefe_r/erlang.d/dryverl-0.1/build-aux/install-sh -d \
    hello_build && cd hello_build && ./hello/configure && \
    make DRYVERL_HOME=./.. \
    PATH=/home/users/okeefe_r/erlang.d/dryverl-0.1/examples/../scripts:\
    .:/home/users/okeefe_r/commands.d:/users/local/bin:/opt/SUNWspro/bin:\
    /usr/ccs/bin:/usr/java1.2/bin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:\
    /usr/ucb:/users/local/teTeX/bin/sparc-sun-solaris2.9:\
    /usr/openwin/bin:/usr/dt/bin:
    /home/users/okeefe_r/export/ghc-4.08.1/tmp/bin:
    /home/users/okeefe_r/export/hbc.d/bin-sparc-solaris2.5/exe:
    /home/users/okeefe_r/export/ocaml-3.00/tmp/bin:
    /home/users/okeefe_r/export/eclipse.d/sparc_sunos5/bin/sparc_sunos5:
    /users/local/mercury/bin dist && \
    mv dryverl_hello-0.1.tar.gz ..
/bin/bash: ./hello/configure: No such file or directory
make[1]: *** [dryverl_hello-0.1.tar.gz] Error 127
make[1]: \
    Leaving directory `/home/users/okeefe_r/erlang.d/dryverl-0.1/examples'
make: *** [all-recursive] Error 1

./examples/hello_build is empty.
There is no ./examples/hello_build/hello/configure,
but there _is_ an examples/hello/configure
I think the line
    hello_build && cd hello_build && ./hello/configure && \
should be
    hello_build && cd hello_build && ../hello/configure && \
                                     ^^

Looking at examples/Makefile, it is quite hard to see what is going on.
I can't quite see where $(srcdir) is set, but wherever it is set, it
is wrong for this example.  Patching the corresponding line of the Makefile
to use ../hello/configure instead of $(srcdir)/hello/configure gets a long
way further.

By the way, six languages in one tool is a little overwhelming.
It would be much simpler for bears of very little brain if interfacing
between Erlang and C only required them to know Erlang, C, and maybe
*one* more notation.




More information about the erlang-questions mailing list