Re: [gentoo-dev] libGLcore error

[Lars Pechan]

On Tue, 04 Jun 2002 16:56, Prashanth Aditya Susarla wrote:
> > It is precisely because it is a precompiled library that it does make a
> > difference. To point out what perhaps is obvious: had it been source we'd
> > never had the problem in the first place.
>
> Ok, thanks for clearing that up. I was under the impression that one has
> to use -lgcc_s while compiling sources so that libgcc_s.so is linked
> dynamically at runtime. Obviously, if we had the sources...
>

That is absolutely correct in the normal case -- unless you state the library 
on the link line you'll get a linker error. The tricky thing in this case is 
that it's the compiler itself that's generating the calls to functions in 
libgcc_s and not the user code directly. libgcc_s contains various 
housekeeping functions the compiler may call depending on the end-user code 
(some refer to it as a junk drawer that contains stuff that doesn't fit 
anywhere else). So as a developer you may not even know you are referencing 
stuff in that lib. 

The older binutils made up for that by re-exporting the symbols that were 
referenced in libgcc_s so you'd end up with a reference to libgcc_s 
implicitly. That does not happen anymore. I believe that if nvidia were to 
take the build environment they used to produce what we have and tries to do 
a build under the new binutils the library won't even build. 

Any linker gurus out there that could let me know if I'm talking shite?

/Lasse