This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Trunk frozen starting tomorrow! No new features!
On Thu, 14 Jun 2012, Mike Frysinger wrote:
> On Thursday 14 June 2012 16:53:46 Roland McGrath wrote:
> > > >> elf/tst-unique3lib.os:(.data.DW.ref.__gxx_personality_v0[DW.ref.__gxx_
> > > >> personality_v0]+0x0): undefined reference to `__gxx_personality_v0'
> > [...]
> > > As I said in my earlier email, it seems unlikely to me that it's possible
> > > to link C++ code built with g++ without using g++ to drive the linker,
> > > but that's exactly what the build rules for these tests seem to do...
> >
> > "Using g++ to drive the linker" means "implicitly adding -lstdc++" AFAIK.
>
> perhaps, but if we require C++ support, it makes sense to me to use g++ rather
> than worrying about what random stuff the driver is doing behind the scenes.
> it's not like executing `gcc -lstdc++` really gains us anything at all over
> `g++`.
But will using g++ actually make any difference, since we link with
-nostdlib, and need to do so in order to link with the newly built glibc
rather than a previously installed one? I suspect -nostdlib means it's
necessary to put -lstdc++ manually on any relevant link line.
--
Joseph S. Myers
joseph@codesourcery.com