[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libtool 2.2.6] testsuite: 40 41 42 43 56 57 58 59 60 61 65 66 68 69
Re: [libtool 2.2.6] testsuite: 40 41 42 43 56 57 58 59 60 61 65 66 68 69 70 71 failed
Mon, 22 Sep 2008 15:51:01 -0500
Thunderbird 22.214.171.124 (X11/20080501)
mark horn wrote:
> To whom it may concern -
Hi Mark, thanks for the report.
> libtool testsuite.log attached, along with output from the sys_log
> listing various libtool tests that crashed
> I'm running OS X 10.3.4 on a G4 PPC
> NOTE: System came with libtool (build dated aug 2004), which was
> resident when build of 2.2.6 failed;
Remember that /usr/bin/libtool on Mac OS X is not the same as
/usr/bin/glibtool. For Mac OS X you should probably run GNU libtool's
configure with --program-prefix=g to ensure that there is no conflict.
> Was trying to compile gnu GUILE assuming resident libtool and libltdl
> would satisfy dependency.
> Guile compile failed with the following error:
> -fprintf$LDBL128 referenced from libltdl expected to be defined in
> /usr/bin/libtool: internal link edit command failed
I don't have a 10.3 system any longer, but, if I recall correctly
fprintf$LDBL128 is defined in libSystemStubs.a, but maybe that is only
on Mac OS X 10.3.9 (which added some things backward compatibility with
> At that point I tried a libtool 2.2.6 build to see if guile problem
> would clear;
> LIBTOOL ./configure and make ran ok... then make check revealed these
> Needless to say, I did NOT run make install for libtool...
Looking at the test failures though, all I see are tests that fail
because your installed autoconf version is 2.58, so all is not as bad as
it looks. If you still wish to use libtool-2.2.6, you can first update
your autoconf and the tests should go more smoothly.
The crashes, are, "on purpose". Changing the crash reporter settings
with /Developer/Applications/Utilities/CrashReporterPrefs.app should
turn them off.
> Any guidance on this greatly appreciated... i.e. any info on what the
> status of my system is at this point, re: stability of "old" libtool /
> libitdl; as well as how to proceed to safely update to libtool 2.2.6 (if
> necessary) so as to get GUILE to compile... so as to get LIBCTL to
> compile... so as to satisfy dependencies for the software I'm ultimately
> hoping to get built, namely MIT mpb and MEEP (numerical codes)...
For patches, you could look at what the MacPorts or Fink packages do,
although as far as I am aware, neither support Mac OS X 10.3 any more.