This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
make check gcc-3_0-branch libstdc++ behaviour
- To: gcc at gcc dot gnu dot org
- Subject: make check gcc-3_0-branch libstdc++ behaviour
- From: Gordon Sadler <gbsadler1 at lcisp dot com>
- Date: Wed, 11 Apr 2001 11:13:25 -0500
I thought? I saw a mention of libstdc++ testing moving to dejagnu? If
this is true, do I need to activate it differently?
As of a few days ago, my test.log is having some odd output from
checking libstdc++:
+ + 27_io/istream_extractor_arith.cc
-r /home/gbsadler/gcc-3.0/i686-pc-linux-gnu/libstdc++-v3/mkcheck: printf: /home/gbsadler/cvs/gcc-3.0/libstdc++-v3/testsuite/27_io/istream_extractor_char.cc:61:: invalid number
-r /home/gbsadler/gcc-3.0/i686-pc-linux-gnu/libstdc++-v3/mkcheck: printf: /home/gbsadler/cvs/gcc-3.0/libstdc++-v3/testsuite/27_io/istream_extractor_char.cc:61:: invalid number
27_io/istream_extractor_char.cc
I'm used to + -b -r et.al. but the printf:...invalid number is all new
here. Maybe the switch to dejagnu is affecting me?
Gordon Sadler