[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libtool 2.2.6] testsuite: 74 failed
From: |
Ralf Wildenhues |
Subject: |
Re: [libtool 2.2.6] testsuite: 74 failed |
Date: |
Sat, 28 Feb 2009 23:32:26 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello Peter, Graham,
* Peter O'Gorman wrote on Wed, Feb 18, 2009 at 03:48:00PM CET:
> Graham Alvare wrote:
> > There's a bug in my libtool, I'm using an almost stock OSX 10.4.11 on an
> > iMac Core2Duo
> > Mac OS X tests
> >
> > 74: darwin fat compile FAILED (darwin.at:93)
>
> > ld: flag: -undefined dynamic_lookup can't be used with
> > MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
> > /usr/bin/libtool: internal link edit command failed
> > lipo: can't figure out the architecture type of: /var/tmp//cclOHQL8.out
> > stdout:
> > libtool: link: (cd
> > /SourceCache/libtool-2.2.6/tests/testsuite.dir/74/.libs/libbar.lax/libfoo.a/unfat-13699/libfoo.a-ppc
> > && ar x "libfoo.a")
> > libtool: link: (cd
> > /SourceCache/libtool-2.2.6/tests/testsuite.dir/74/.libs/libbar.lax/libfoo.a/unfat-13699/libfoo.a-i386
> > && ar x "libfoo.a")
> > libtool: link: gcc -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o
> > .libs/libbar.0.dylib .libs/bar.o .libs/libbar.lax/libfoo.a/baz.o
> > .libs/libbar.lax/libfoo.a/foo.o -arch ppc -arch i386 -install_name
> > /nonexistent/libbar.0.dylib -compatibility_version 1 -current_version 1.0
> > -Wl,-single_module
> > ./darwin.at:93: exit code was 1, expected 0
> > 74. darwin.at:26: 74. darwin fat compile (darwin.at:26): FAILED
> > (darwin.at:93)
>
> Thanks for this, your libtool is fine, but there is a bug in the
> testsuite. The test should either skip in this case, or set
> MACOSX_DEPLOYMENT_TARGET.
Any chance you could suggest a patch?
> By the way, whenever you build with libtool on ppc Mac OS X < 10.5, you
> should set the environment variable MACOSX_DEPLOYMENT_TARGET=$OS_VERSION
> unless you are targetting an earlier OS than you are building on.
Should this be mentioned more explicitly in doc/notes.texi, too?
Thanks!
Ralf