On Wed, Aug 30, 2000 at 12:23:07PM +0300, Mats Nygren wrote:
Thanks, but I don't yet get it. Could you add a little information? I tried your line and then "make" and got the following:
Furthermore the following first line in aclocal.m4 worries me:
dnl aclocal.m4 generated automatically by aclocal 1.4
is this really generated automatically, if so shouldn't the change be made somewhere else?
Yes, you are right. aclocal.m4 is generated from acinclude.m4 and configure.in with "aclocal".
The whole automake/autoconf/configure stuff is somewhat complex, so here some more information:
The Makefile is build from "Makefile.in" with the help of the "configure" script. "configure" is generated by "autoconf" from "configure.in" and aclocal.m4. And aclocal.m4 is generated with "aclocal" (part of GNU automake) from acinclude.m4 and configure.in. Wow.
So... normally you only need to run "configure". But if you change configure.in you need to get autoconf
http://www.gnu.org/software/autoconf/autoconf.html
and call "autoconf" in the unix-src directory to rebuild "configure".
and if you want to rebuild aclocal.m4 (you changed acinclude.m4) you need automake:
http://www.gnu.org/software/automake/automake.html
and use aclocal to rebuild aclocal.m4
what is libffi? a standard unix facility?
No. And even not available in most Linux distributions.
You can get it from
http://sources.redhat.com/libffi/
It's only needed for compiling Squeak (it's linked statically because it's not that big).
The real bug in the build-process seems to be that the FFI-Plugin gets compiled even if libffi is not available on the system.
Marcus
squeak-dev@lists.squeakfoundation.org