------- Comment #11 from developer at sandoe-acoustics dot co dot uk 2009-09-23 16:00 ------- (In reply to comment #10) > What about just leveraging PIC-code libgcc.a on darwin by creating a > libgcc_ext > with only a dummy routine and a linkage to the FSF libgcc.a. When creating > libgcc_ext, the ld option -unexported_symbols_list would be used and a file > containing all of the symbols exported from libgcc_10.5 passed to it.
as far as an _ext is concerned - I don't think there's any issue with what I proposed - it also should extend to fill any gaps in 10.6 (we just leave libgcc_s out of the link line I guess). The issue is whether there's a Better Way to do the job. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39888
