This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libstdc++ libtool lossage




--On Saturday, February 23, 2002 08:20:30 PM -0300 Alexandre Oliva 
<aoliva@redhat.com> wrote:

Thanks for your answer.  I'm still trying to get my head around all
of it, but, if you would be so kind, I have a few more preliminary
questions.

>> gcc and g++ handled "-shared" differently because it was thought that
>> C users would benefit from not having to deal with the shared libgcc,
>
> No, they didn't, but they do now, on GNU/Linux, if you have a recent
> enough version of GNU ld.

Are you saying that, until recently, both "gcc -shared" and
"g++ -shared" linked the shared library with both the shared libgcc and
the static one? (That sound plausible, just not what I remembered.)

(Parenthetically, that suggests that my memory was probably of the
executable creation behavior; when linking a final executable "gcc"
linked in the static libgcc but "g++" linked in the shared libgcc?
(And also the static one, or not?)  Is this right?)

And you're saying that now some bit of binutils wizardy means that
on sufficiently modern GNU/Linux machines we could created C shared
libraries without linking with any libgcc at all?  Or by linking with
just the static version; we no longer need the shared version?

Just trying to catch up,

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]