This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: bootstrap failure (libstdc++ testsuite_hooks)
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: gcc at gcc dot gnu dot org, Gabriel Dos Reis <gdr at integrable-solutions dot net>,libstdc++ at gcc dot gnu dot org
- Date: Fri, 20 Jun 2003 12:25:04 +0200 (CEST)
- Subject: Re: bootstrap failure (libstdc++ testsuite_hooks)
- References: <Pine.BSF.4.55.0306200025290.61043@acrux.dbai.tuwien.ac.at><u8vfv18hn9.fsf@gromit.moeb>
On Fri, 20 Jun 2003, Andreas Jaeger wrote:
> This is on mainline? I successfully bootstrapped and run the
> testsuite yesterday several times on both i686-linux and x86_64-linux.
Yes.
> What's the output of:
> /tmp/OBJ-0619-2203/i686-pc-linux-gnu/libstdc++-v3/scripts/testsuite_flags --build-cxx
> ?
% /files/pfeifer/OBJ-0620-1125/i386-unknown-freebsd4.8/libstdc++-v3/scripts/testsuite_flags --build-cxx
%
No output at all, because -- as I just realized -- the script is
completely empty -- filesize zero. Checking my build log, I also
realize why!
creating scripts/testsuite_flags
sed: /sw/test/gcc/cvs/libstdc++-v3/scripts/testsuite_flags.in: No such file or directory
There seem to be two problems here:
1) The scripts Gaby, me (and surely several others) use to build GCC
failed to update the new directories from CVS; this is most probably
related to us not using the -d option of `cvs update` globally to
avoid getting Ada.
2) Still, failure to locate this file should have aborted bootstrap
immediately; would you mind fixing that?
Gerald