This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: outdated dejagnu information on http://gcc.gnu.org/install/test.html
- To: jsm28 at cam dot ac dot uk
- Subject: Re: outdated dejagnu information on http://gcc.gnu.org/install/test.html
- From: Laurent Guerby <guerby at acm dot org>
- Date: Sat, 24 Feb 2001 20:11:29 +0100
- CC: pfeifer at dbai dot tuwien dot ac dot at, kraai at alumni dot carnegiemellon dot edu, gcc at gcc dot gnu dot org
- References: <Pine.LNX.4.32.0102241817380.8757-100000@kern.srcf.societies.cam.ac.uk>
- Reply-to: guerby at acm dot org
[Switched from gcc-patches to gcc]
Joseph S. Myers wrote:
> [...] I don't know whether this is a dejagnu problem, or a tcl/expect one;
> dejagnu 1.4 doesn't come with its own tcl/expect, whereas the previous
> dejagnu snapshot was using its own tcl/expect.
I just ran make check after installing dejagnu 1.4 (i386 RPM from
ftp.gnu.org on a RedHat 6.1 x86 box), I sent the results to
gcc-testresults@gcc.gnu.org as documented (I can send them to you if
you want). The only "gcc.dg" failures I got were:
FAIL: gcc.dg/20000724-1.c execution test
FAIL: gcc.dg/20001117-1.c (test for excess errors)
FAIL: gcc.dg/sequence-pt-1.c sequence point warning (test for warnings, line 59)
FAIL: gcc.dg/special/weak-1.c execution test
This is my first run of make check, I never messed with Tcl/Tk or
DejaGnu before.
BTW, I built my compiler from CVS HEAD, and I configured in a separate
build dir from the "top-level" configure (ie the one at the same level
as the libchill/f2c/ffi/iberty/... that has another gcc subdir in it).
Is it the right thing to do? Or should I use the configure from gcc/gcc?
--
Laurent Guerby <guerby@acm.org>