From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-01-29 01:56:00
Michael Stevens wrote:
> Rene Rivera wrote:
> ering why the gcc toolset links with g++, even for C code.
>
> > > At home I only need to compile C code, and so I only downloaded the
> > > gcc binaries; I did not bother to download the g++ binaries. When I
> > > ran bjam, it died because there was no g++.
> > >
> > > It's not a big deal (I can change the toolset or download g++), but
> > > was curious why the toolset was designed this way.
> >
> > Simply put because there's no way to know when we do the link if all the
> > sources (.o, .so, .lib, .dll, etc) are only C.
>
> Related to this, does anyone know exactly what effect the g++ invokation
> has on GCC? Clearly it adds "stdc++" to the list of link libraries.
And -lm as well ;-)
And it also changes the name of some gcc-internal library from lgcc_eh to
lgcc_s -- not that I know what either one does.
That's the only differences that can be seen when gcc is run with -v option.
- Volodya