Benjamin Herbert wrote: []
Haven't seen this for a while. If I remember correctly, this used to be caused by a spurious gcc.dylib sitting around in /usr/local/lib. Do you have such a thing?Yes, libgcc.dylib does exist in /usr/local/lib. How is this breaking the build?
Well, there is a "-lgcc" on every linker command line(*). It is supposed to result in linking to the static library /usr/lib/libgcc.a. But when the Apple linker sees a dynamic library libgcc.dylib anywhere on its search path, like the /usr/local/lib/libgcc.dylib you are having, it takes the dynamic lib instead of the static lib. The symbol __eprintf is defined in /usr/lib/libgcc.a, but apparently not in your /usr/local/lib/libgcc.dylib. Hence breakage.
What this means is that any software that installs /usr/local/lib/libgcc.dylib on your Mac has been brewed together by some antisocial idiots that don't understand MacOSX and don't care whether your system breaks, as long as their stuff is working. You should complain to them.
--
Martin
(*) Run "gcc -v program.c" to see the complete compiler and linker command lines.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
