thanks. The Guile team is working on Libtool 2.2.x migration, and I
think it will take a while before it got fully integrated.
thanks.
steve
On Apr 16, 2008, at 3:17 PM, Ralf Wildenhues wrote:
Steven, please keep the libtool list in CC:, thanks.
* Steven Wu wrote on Mon, Apr 14, 2008 at 04:04:39AM CEST:
On Apr 13, 2008, at 10:12 AM, Ralf Wildenhues wrote:
[ re-adding libtool list in Cc: ]
* Steven Wu wrote on Sun, Apr 13, 2008 at 06:43:59PM CEST:
In libguile/.libs/guileS.o
$ nm -p libguile/.libs/guileS.o
00000224 S _lt_preloaded_symbols
this doesn't seem to be correct.
Ah ok, thanks. That means that linking of guile is done by libtool
1.5.x, not 2.2.x.
We may need to document this better: using libltdl from 2.2.x
requires
libtool 2.2.x to link against.
So how can I ensure that the libtool 2.2.x is being used? Since I
am on
MacOS X, and the darwin's libtool is shipped with the OS. I
installed the
latest release of gnu libtool, and I named the executable to be
glibtool.
What should I do to build guile with the right stuffs?
As a hack, you can try
make LIBTOOL=glibtool
but to update properly, you need to replace the libtool.m4 and other
macro files in the package (the Libtool macros may have been copied
into
the acinclude.m4 or aclocal.m4 files), and replace ltmain.sh with the
2.2.2 version, and then regenerate configure. Typically, libtoolize
does part of this, and often, autoreconf --force can do all of it for
you. If the package has a custom ./bootstrap or ./autogen.sh, then
that is the way to go.
Cheers,
Ralf
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
