This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++ testsuite fixes, 1
- To: "Zack Weinberg" <zackw at stanford dot edu>
- Subject: Re: libstdc++ testsuite fixes, 1
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Date: 15 May 2001 21:15:13 +0200
- Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <20010515112504.P774@stanford.edu>
"Zack Weinberg" <zackw@stanford.edu> writes:
| If you build using a relative pathname to get from the object to the
| source directory, testsuite_flags --build-includes will generate -I
| switches which are relative to the top level of the libstdc++ build
| directory. runtest executes one level below (in the testsuite
| directory), therefore all the paths are wrong, and the test suite
| can't find any headers and blows up horribly.
Hmm. I'd rather we fix the problem differently.
The just-removed libstdc++.exp used to do the follwoing
# Get the source and the build directories.
set src-dir [lookfor_file $srcdir libstdc++-v3]
set build-dir [lookfor_file $outdir libstdc++-v3]
I'll prefer we get that functionality back.
Thanks,
-- Gaby