Ralf Wildenhues wrote:
In case anyone is wondering (Gary) why HEAD fails one of the new tests on Mac OS X 10.4, it is because of a bug in the linker. I have reported the bug and it is unlikely to be fixed before Mac OS X 10.5, I think.


Which one fails, and how?  Just so we can distinguish it easily from
genuine failures.

Hi Ralf, sorry, had to rerun the testsuite because my memory was not good enough to remember "template test with subdirs", failure is here:

../../libtool/tests/template.at:212: $LIBTOOL --tag=CXX --mode=link $CXX $CXXFLAGS -o sub/main sub/main.o lib2/libb.la lib/liba.la + /Users/peter/cvsco.build/lttst/libtool --tag=CXX --mode=link g++ -g -O2 -o sub/main sub/main.o lib2/libb.la lib/liba.la
stderr:
stdout:
libtool: link: g++ -g -O2 -o sub/.libs/main sub/main.o -Wl,-bind_at_load lib2/.libs/libb.dylib lib/.libs/liba.a
libtool: link: creating sub/main
+ set +x
../../libtool/tests/template.at:213: if ./sub/main; then :;
           elif test "X$host" != "X$build" && \
                { test -x "./sub/main" || test -x "./sub/main"$EXEEXT; }
           then (exit 77); fi
Not enabling shell tracing (command contains an embedded newline)
--- /dev/null   2005-06-17 23:27:11.000000000 +0900
+++ /Users/peter/cvsco.build/lttst/tests/testsuite.dir/at-stderr 2005-06-17 23:27:12.000000000 +0900
@@ -0,0 +1,9 @@
+dyld: lazy symbol binding failed: Symbol not found: __Z2a2c
+ Referenced from: /Users/peter/cvsco.build/lttst/tests/testsuite.dir/14/obj/lib2/.libs/libb.0.dylib
+  Expected in: flat namespace
+
+dyld: Symbol not found: __Z2a2c
+ Referenced from: /Users/peter/cvsco.build/lttst/tests/testsuite.dir/14/obj/lib2/.libs/libb.0.dylib
+  Expected in: flat namespace
+
+/Users/peter/cvsco.build/libtool/tests/testsuite: line 6014: 9018 Trace/BPT trap ./sub/main
14. template.at:124:  FAILED (template.at:213)

Note that this looks like a bug in the dynamic linker (dyld) it is not, the bug is in ld.


There is a pretty good workaround though, set the MACOSX_DEPLOYMENT_TARGET environment variable to 10.3 or later and ./configure; make; make check will pass all tests.


Thanks for this information.  Should this be in doc/notes.texi?

Dunno, what do you think?

Peter
--
Peter O'Gorman - http://www.pogma.com


_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool

Reply via email to