On Mon, Dec 15, 2008 at 11:12:41PM +0100, James E. Bailey said: > > Am 15.12.2008 um 22:58 schrieb Joshua Root: > >> Bryan Blackburn wrote: >>> On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said: >>> [...] >>>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile >>> [...] >>>> (cd .libs && /usr/bin/gcc-4.0 -O2 -c -fno-builtin "guileS.c") >>>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT >>>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - >>>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - >>>> D_THREAD_SAFE -o .libs/guile guile-guile.o -L/opt/local/lib >>>> ./.libs/ >>>> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl >>>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols: >>>> _lt__PROGRAM__LTX_preloaded_symbols >>>> collect2: ld returned 1 exit status >>> >>> Do you have libtool2 someplace? Either one of the ports (libtool- >>> devel and >>> libtool2) or somewhere else? >> >> There actually isn't a libtool2. The libtool port is meant to be >> updated >> to 2.x soon, but it hasn't happened yet. Could still be libtool-devel, >> of course. >> >> - Josh > > Yes, I have libtool 2.2.6 installed. I usually just build things myself, > outside of guile. Is libtool 2 a problem? Shouldn't macports build and > configure things itself, regardless of what I have installed in /usr/local > and ~/ ?
The first hit when googling lt__PROGRAM__LTX_preloaded_symbols is about building guile, and suggests it may be an incompatibility issue with libtool2. Having stuff in /usr/local is problematic because some tools like to look there regardless of what port says, eg, the -lltdl in the above compile line may be picking up libtool2's version in /usr/local. Bryan _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
