Hi,
I've been building gcc-4.2 on my mac for about a week now. The first try
timed out, so I decided to continue the build manually. That failed last
night, since my router had its daily crash and I did not run the build in a
a screen session. When I continue the build again, I am afraid it will start
all the tests again, which takes forever... I'd prefer not to do that on a
slow mac. Is there a faster way to finish the build or should I just give
the package back and let a faster buildd handle it? Maybe the current build
stage is of use to somebody? I assume if it is running tests now, that the
actual build has succeeded?
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /build/buildd/gcc-4.2-4.2-20070516/src/gcc/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/build/buildd/gcc-4.2-4.2-20070516/src/gcc/testsuite/gcc.c-torture/compile/compile.exp
...
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c -O2 (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c -O3 -fomit-frame-pointer (test for
excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c -O3 -g (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c -Os (test for excess errors)
Running
/build/buildd/gcc-4.2-4.2-20070516/src/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
...
Running
/build/buildd/gcc-4.2-4.2-20070516/src/gcc/testsuite/gcc.c-torture/execute/execute.exp
...
FAIL: gcc.c-torture/execute/20020418-1.c execution, -O1
FAIL: gcc.c-torture/execute/20020418-1.c execution, -O2
FAIL: gcc.c-torture/execute/20020418-1.c execution, -Os
Christian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
