Re: [PATCH, DARWIN] fix emutls exports in libgcc_s10.{4,5}.dylib

[IainS <developer at sandoe-acoustics dot co dot uk>]

On 10 Dec 2008, at 14:43, Jack Howarth wrote:

> shipped by Apple with its OS releases. I think what you want to do
> make sure you are using the FSF libgcc's and not the system ones
> while having environmental MACOSX_DEPLOYMENT_TARGET unset. The latter
> step will cause the unversioned libgcc to be used with all the newer
> symbols specific to the FSF gcc 4.4 release (that are not listed in
> the darwin-libgcc.10.4.ver and darwin-libgcc.10.5.ver files).

I have not found a way (MACOSX_DEPLOYMENT_TARGET set or unset) of  
getting the loader to look at the FSF libgcc_s.1.dylib unless I  
specifically name it on the command line with -lgcc_s.1

That does work ( as does -lgcc_eh. )

I guess I misunderstood the purpose of libgcc_s10.x as being "all the  
symbols added since this release"

It would help if someone could point me at some clear documentation  
about what

libgcc_eh
libgcc_s.1
libgcc_s.10.X

*should* contain.

other than that, it's a case of returning to some solution which  
involves a tls.exp... etc.

thanks,
Iain