------- Comment #9 from howarth at nitro dot med dot uc dot edu 2009-09-23
03:02 -------
(In reply to comment #6)
> I wonder if we could just trim out the symbols from libgcc that are in
> libSystem, and arrange for gcc's installed libgcc to be found first.
Mike,
Remember on llvm-dev Nick said...
On a SnowLeopard system you *can* link against /usr/lib/libgcc_s.
10.5.dylib, but the linker will not record any symbols coming from
it. In fact, the link order does not matter. That is because /usr/
lib/libgcc_s.10.5.dylib has magic symbols in it that say if you are
targeting 10.6 then _Unwind_Resume (and other other symbols) are not
in that dylib, so the linker looks elsewhere and finds them in
libSystem.B.dylib. In other words, the compiler changes to
SnowLeopard to omit /re-order the linking with -lgcc_s when targeting
10.6 was just an optimization and not required.
Doesn't this imply that you can't make force libgcc to be found before
libSystem under SL?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39888
