------- Comment #8 from mrs at apple dot com 2009-09-22 21:17 ------- I meant the idea that libSystem has new symbols in it is relevant only to darwin10. The system libgcc_s is present on older OSes, so those aspects are still relevant. Yeah, to solve that problem one would either have to have a new name, or possibly an explicit path. I've not tried the later, but it might offer a way to construct the library with fewer mods.
from darwin10: $ nm /usr/lib/libgcc_s.1.dylib | grep Unwind_Bac 0019f9c6 S $ld$hide$os10.4$__Unwind_Backtrace 0019f9c7 S $ld$hide$os10.5$__Unwind_Backtrace 00163b30 T __Unwind_Backtrace $ nm /usr/lib/libSystem.dylib | grep Unwind_Bac 0019f9c6 S $ld$hide$os10.4$__Unwind_Backtrace 0019f9c7 S $ld$hide$os10.5$__Unwind_Backtrace 00163b30 T __Unwind_Backtrace also note, there is add as well as hide; $ nm /usr/lib/libgcc_s.10.5.dylib | grep Unwind_Back 00000f0a S $ld$add$os10.4$__Unwind_Backtrace 00000f0b S $ld$add$os10.5$__Unwind_Backtrace As for what functions (symbols), well, the ones in common between libSystem/libgcc_s on the system and libgcc from gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39888
