This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++ summary
- From: Phil Edwards <phil at jaj dot com>
- To: Mike Cleary <mcleary at iol dot unh dot edu>
- Cc: libstdc++ at gcc dot gnu dot org, clp <clp at iol dot unh dot edu>
- Date: Mon, 16 Dec 2002 18:59:21 -0500
- Subject: Re: libstdc++ summary
- References: <3DFE271E.7000605@iol.unh.edu>
On Mon, Dec 16, 2002 at 02:18:54PM -0500, Mike Cleary wrote:
> Greetings,
> I have the following summary to report on libstdc++. I was just
> wondering if someone can tell me where to look to find the exact error
> so that I can report that. I've found this on an alpha with the
> alphaev56 configuration in the basic baseline with the gcc-3_2-branch:
>
> === libstdc++-v3 Summary ===
>
> # of expected passes 397
> # of unexpected failures 9
> # of unexpected successes 10
> # of expected failures 16
> make[4]: *** [check-DEJAGNU] Error 1
alphaev56-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++-v3.log
> make[4]: Leaving directory
> `/mnt/u9/toolchain/buildsys/build/alpha9/basic/native/gcc-
> 3_2-branch/alphaev56-unknown-linux-gnu/libstdc++-v3/testsuite'
> make[3]: *** [check-am] Error 2
> make[3]: Target `check' not remade because of errors.
This is why the instructions say to use 'make -k check'. DejaGNU incorrectly
kill the make chain by passing back an error status, which means that any
subsequent targets in the makefile are not done.
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002