Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

[Andreas Florath]

Hello!

Please help me! I have problems running the tests for egcs-971114 on an alpha-dec-osf4.0.
I got the egcs-971114.tar.gz from the server, unpacked it, applied the latest alpha
patches and made a bootstrap. This all works fine.
Then I typed: "cd gcc ; make -k check" and after running a while, the following output
appaered:
[FAILures deleted]
FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O1 
FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O2 
FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O2 -fomit-frame-pointer -finline-functions 
ERROR: tcl error sourcing /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/execute.exp.
ERROR: child process exited abnormally
    while executing
"exec rm -f $x"
    ("foreach" body line 3)
    invoked from within
"foreach x $args {
                    if { [file exists $x] && [file isfile $x] } {
                        exec rm -f $x;
                    }
                }"
    ("delete" arm line 2)
    invoked from within
"switch $op {
            cmp {
                set otherfile [lindex $args 1];
                if { [file exists $file] && [file exists $otherfile]
                     && [file size $file] == [file ..."
    (procedure "standard_file" line 5)
    invoked from within
"standard_file "twister" delete /tmp/complex-5.x"
    ("eval" body line 1)
    invoked from within
"eval ${try}_${proc} \"$dest\" $args"
    (procedure "call_remote" line 57)
    invoked from within
"call_remote "" file "build" delete /tmp/complex-5.x"
    ("eval" body line 1)
    invoked from within
"eval call_remote \"\" file \"$dest\" $args"
    (procedure "remote_file" line 2)
    invoked from within
"remote_file build delete $executable"
    (procedure "c-torture-execute" line 40)
    invoked from within
"c-torture-execute $src"
    ("foreach" body line 7)
    invoked from within
"foreach src [lsort [glob -nocomplain $srcdir/$subdir/*.c]] {
    # If we're only testing specific files and this isn't one of them, skip it.
    if ![..."
    (file "/misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/execute.exp" line 39)
    invoked from within
"source /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/execute.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/execute.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""
Running /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp ...
ERROR: tcl error sourcing /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp.
ERROR: child process exited abnormally
    while executing
"exec rm -f $x"
    ("foreach" body line 3)
    invoked from within
"foreach x $args {
[more or less as above]

I use dejagnu-971028 and the last weeks test were ok (no such output appeared).

Have I forgotten something? Have I made a mistake? How can I solve this?


I'm quiet new using dejagnu. All my tests start with the lines:
Test Run By af on Wed Nov 19 13:54:22 1997
Target is alpha-dec-osf4.0
Host   is alpha-dec-osf4.0b

                === gcc tests ===

Running target unix
Using /usr/local/pkg/dejagnu-971028/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/pkg/dejagnu-971028/share/dejagnu/config/unix.exp as generic interface file for target.
Using /misc/home/af/EGCS/egcs-971114/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
WARNING: Assuming target board is the local machine (which is probably wrong).
You may need to set your DEJAGNU environment variable.
Running /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/code_quality/code_quality.exp ...
Running /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
[...]

Is this ok? Did I made a mistake during the dejagnu's installation process?

Please help - then I can run the tests for the 971114!

Regards
Andre

Re: Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

[Jeffrey A Law]

  In message < 3472FDE0.FB6D309B@gamic.com >you write:
  > patches and made a bootstrap. This all works fine.
Good.

  > Then I typed: "cd gcc ; make -k check" and after running a while, the follo
  > wing output
  > appaered:
  > [FAILures deleted]
  > FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O1 
  > FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O2 
  > FAIL: gcc.c-torture/execute/970214-2.c compilation,  -O2 -fomit-frame-point
  > er -finline-functions 
  > ERROR: tcl error sourcing /misc/home/af/EGCS/egcs-971114/gcc/testsuite/gcc.
  > c-torture/execute/execute.exp.
  > ERROR: child process exited abnormally
This usually means the "expect" program exited for some strange reason;
you might grope around for a core file and see what process it came
from.

jeff

Re^2: Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

[Andreas Florath]

Hello!

Jeffrey A Law wrote:
> [stuff deleted]
> This usually means the "expect" program exited for some strange reason;
> you might grope around for a core file and see what process it came
> from.
> 
> jeff
Yep - there is a core around. It was generated from '961004-1.x' :-)
(I think this would not help anything - to bad!)

Andre

Re: Re^2: Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

[Jeffrey A Law]

  In message < 347AC6B6.1BA087A1@gamic.com >you write:
  > > 
  > > jeff
  > Yep - there is a core around. It was generated from '961004-1.x' :-)
  > (I think this would not help anything - to bad!)
Hmmm, a test core dumping shouldn't cause the testsuite to crash --
otherwise we'd never get anywhere  :-) :-)

Probably something else, though it's going to be awful hard to track
down.

jeff

Re: Re^2: Help needed: problems with 'make check' (in gcc) on alpha-dec-osf4.0

[Andreas Florath]

Hello!

Jeffrey A Law wrote:
> Probably something else, though it's going to be awful hard to track
> down.
> 
> jeff

Yes, I understand.  Yesterday I had a closer look where 'expect' fails: it fails in 
'complex-5.c'.  I rebuild the latest dejagnu release (971028) and the 'make check' in
dejagnu failed!  I sent a bug report to bug-dejagnu and now waiting for answers.

Andre