This is the mail archive of the
mailing list for the libstdc++ project.
Re: include/g++-v3/c++ path with libstdc++ under gcc 3.1
- From: Phil Edwards <phil at jaj dot com>
- To: Christoph Bugel <chris at tti-telecom dot com>
- Cc: John Clinton <j dot clinton at aristoslogic dot com>, libstdc++ at gcc dot gnu dot org
- Date: Fri, 31 May 2002 18:33:37 -0400
- Subject: Re: include/g++-v3/c++ path with libstdc++ under gcc 3.1
- References: <20020530214621.GA27666@pingu.tti>
On Fri, May 31, 2002 at 12:46:21AM +0300, Christoph Bugel wrote:
> On 2002-05-30 John Clinton wrote:
> > ..../include/g++-v3/c++/bits/c++config.h
> > instead of
> > ..../include/g++-v3/bits/c++config.h
That's definitely user error...
> > ../gcc-3.1/configure --prefix=/proj/alctools/gcc/linux_i386_$ver --disable-s
> > hared --enable-static --enable-long-long --enable-languages="c c++"
> The correct syntax is: --enable-languages=c,c++
> (or simply --enable-languages=c++ because C is enabled by default)
We checked in a patch last year to accept space-separated languages
because so many people were making this error. (You are still correct
in what should have been typed.) I'm amazed that this could show up as
extra directories in an installation path.
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams