From: "Paweł Sikora" <pluto@pld-linux.org>
To: gcc-help@gcc.gnu.org
Subject: problems with `make -k check`
Date: Mon, 25 Jul 2005 07:21:00 -0000 [thread overview]
Message-ID: <200507250919.33134.pluto@pld-linux.org> (raw)
Hi,
I've installed autogen-5.7 and dejagnu-1.4.4 but `make -k check`
reports tons of failures :|
=== 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 /home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC/gcc/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running /home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
set_ld_library_path_env_vars:
ld_library_path=:/home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC/obj-x86_64-pld-linux/gcc
Executing on
host: /home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC.backup/obj-x86_64-pld-linux/gcc/xgcc
-B/home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC.backup/obj-x86_64-pld-linux/gcc/
-O0 -w -fno-show-column -c -o 20000105-1.o
/home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
(timeout = 300)
compiler exited with status -1
output is:
spawn failed
FAIL: gcc.c-torture/compile/20000105-1.c -O0 (test for excess errors)
Excess errors:
spawn failed
(...)
compilation of the testunit works fine:
LD_LIBRARY_PATH=/home/users/pluto/rpm/BUILD/gcc-4.1-20050724T0642UTC/obj-x86_64-pld-linux/gcc
gcc/xgcc -Bgcc/ -O0 -w -fno-show-column -c -o 20000105-1.c
../gcc/testsuite/gcc.c-torture/compile/20000105-1.c
what is wrong with my enviroment?
--
The only thing necessary for the triumph of evil
is for good men to do nothing.
- Edmund Burke
reply other threads:[~2005-07-25 7:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507250919.33134.pluto@pld-linux.org \
--to=pluto@pld-linux.org \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).