This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Disabling libstdc++-v3
- To: Steinar Bang <sb at metis dot no>
- Subject: Re: Disabling libstdc++-v3
- From: Bo Thorsen <bo at sonofthor dot dk>
- Date: Fri, 15 Dec 2000 10:16:32 +0100 (MET)
- Cc: gcc at gcc dot gnu dot org
On 15 Dec 2000, Steinar Bang wrote:
> >>>>> Ghadi Shayban <shaybang@yahoo.com>:
>
> > I used to be able to compile Mozilla from using gcc from CVS. Then
> > the switch to libstdc++-v3 occured. For a couple of days, I could
> > still compile gcc and use it on mozilla if I used the
> > --disable-libstdcxx-v3 option. But for a while now, the build has
> > failed. It's a little disappointing because the speed improvement
> > with the new gcc was spectacular.
>
> I'm curious: why does the choice of libstc++ affect Mozilla? I
> thought Mozilla was written in plain old C?
Even when you compile gcc with --enable-languages=c, libstdc++ is
compiled. If you don't want this you can simply delete the libstdc++
directory before you run configure. Just don't forget to only compile for
c support. Currently with x86-64 development I delete fastjar, libjava,
texinfo, libstdc++, texinfo, zlib and boehm-gcc for faster compilation
during development.
Bo.
--
Bo Thorsen
bo@sonofthor.dk
Lahnsgade 31, st.
DK-5000 Odense C
Tlf: +45 66 11 83 85
Rule one of good programmers: anything You can do, I can do better
Rule two of good programmers: anything I can do, You can do better
The Programming Theorem: anything worth doing is worth doing over and over again