------- Comment #4 from howarth at nitro dot med dot uc dot edu 2009-11-28 21:09 ------- Doh! I bet this is caused by Iain's libgcc_ext patch.
http://gcc.gnu.org/viewcvs/trunk/libgcc/config/t-slibgcc-darwin?r1=154282&r2=154281&pathrev=154282 Specifically the section... INSTALL_FILES=libgcc_s.10.4.dylib libgcc_s.10.5.dylib libgcc_s.1.dylib +# we're only going to build the stubs if the target slib is /usr/lib +# there is no other case in which they're useful in a live system. +ifeq (/usr/lib,$(shlib_slibdir)) +LGCC_STUBS = libgcc_s.10.4.dylib libgcc_s.10.5.dylib +else +LGCC_STUBS = +endif I don't think this was properly thought through. By not building the stubs, the ones in /usr/lib get used and we start linking in two different libgcc's. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42208
