Re: libstdc++ V3 install runs into problems.

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

Benjamin Kosnik wrote:

> It looks like I missed checking in two subdirs to the
> libstdc++-v3/shadow directory on Friday: I just fixed this error. This
> probably accounts for your earlier problems. If you do a 'cvs update -d'
> in the libstdc++-v3 subdirectory, the shadow/bits and shadow/sys
> directories will be populated.

Yep - it works now.

> However.
> 
> Current CVS g++ + libstdc++-v3 is not building, due to a new compiler
> error (last successful build == April 20).
> 
> (from CVS as of a few minutes ago, hosted on x86-linux with
> --enable-libstdcxx-v3)

[ abort in flow deleted ]

Looks like a real problem to me - on i586-pc-linux-gnu; I'm using
i686-pc-linux-gnu.  I've built yesterday's CVS snapshot and today's
(this morning) without problems.  This is on Debian 2.1 GNU/Linux (the
boxed set) using:

Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/specs
gcc version 2.95.3 19991030 (prerelease)

for the initial compiler and

../egcs/configure --prefix=/usr/snp --enable-libstdcxx-v3

for configure (no special BOOT_CFLAGS).

On my Alpha (alphaev6-unknown-linux-gnu, running Red Hat 6.0 Linux),
using the same initial compiler and the same configure flags (and no
special BOOT_CFLAGS) and after rth's "c++ template asm fix" was applied,
everything went smooth ... no complaints. 

[ I can see now why C++ afficionados want fast compilers - twice in a
  row I fell asleep while waiting for libstdc++v3 to be compiled ... ]

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://xena.eas.asu.edu/~andy (under construction)