Martin Costabel wrote:
I think we can safely blame this on libtool. The -all_load flag that it
adds will break any gcc linker command when MACOSX_DEPLOYMENT_TARGET is
set to 10.4, because then both -lgcc_s.10.4 and -lgcc are present on the
linker line and when -all_load hits libgcc.a, the above multiple
definition error will result. In addition, -all_load is not even needed
here. This has been discussed for other packages in the past, but I
don't remember the conclusion.
Hi Martin, thanks for the CC.
If libtool's whole_archive_flag_spec is set to the empty string then libtool
will unpack convenience libraries and add the objects to the link line. This
was done in libtool-1.5.8 (albeit for a different reason). sedding the
generated libtool script after the configure stage to remove all_load should
do the trick.
e.g.
./configure %c
sed -i -e \
's/^whole_archive_flag_spec=.*/whole_archive_flag_spec=""/g;' \
libtool
Note that if you are building fat then you must update to a recent libtool,
ar x does not work on ranlibbed fat archives. I'd suggest the latest libtool
version because while I added code to libtool to unpack fat archives for
1.5.8, it had a few flaws, the latest version is better :)
Peter
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users
