The toolchain, when built on Linux, incorrectly links libgcc_s.10.4.dylib.tmp,
resulting in a corrupt
binary when run through strip (the magic number is wrong!) Unknown why this
occurs.
On Linux some symbols in libgcc_s.10.4.dylib.tmp are not marked external (div0,
etc), while they
are on OS X. Maybe this has something to do with it?
Original issue reported on code.google.com by nightwat...@gmail.com on 13 Sep 2007 at 8:06
Original issue reported on code.google.com by
nightwat...@gmail.com
on 13 Sep 2007 at 8:06