Gary V. Vaughan wrote:
So the better workaround is to add 'export
MACOSX_DEPLOYMENT_TARGET=10.3' to
those tests rather than skip them altogether?
Hmm, no, you have to do it before you configure and build libtool. There are
other workarounds to the ld bug, but they'd involve me adding a bunch more
darwin specific bits to ltmain.m4sh and we'd probably all rather that I
avoid that.
The test is correct, the linker is broken, but in this case, if both liba
and libb are shared, or both are static, then the test passes. It only fails
for shared libb with static liba. This situation seems fairly unlikely in
the real world, so skipping the test is probably appropriate.
Peter
