public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/43441] New: pr42427.c:5:21: fatal error: complex.h: No such file or directory Date: Fri, 19 Mar 2010 14:01:00 -0000 [thread overview] Message-ID: <bug-43441-276@http.gcc.gnu.org/bugzilla/> (raw) Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ - O2 -fexceptions -fnon-call-exceptions -fpeel-loops -c -o pr42427.o /test/gnu/gc c/gcc/gcc/testsuite/gcc.dg/pr42427.c (timeout = 300) /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/pr42427.c:5:21: fatal error: complex.h: N o such file or directory compilation terminated. compiler exited with status 1 output is: /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/pr42427.c:5:21: fatal error: complex.h: N o such file or directory compilation terminated. FAIL: gcc.dg/pr42427.c (test for excess errors) -bash-3.2$ less /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/pr42427.c /* { dg-do assemble } */ /* { dg-options "-O2 -fexceptions -fnon-call-exceptions -fpeel-loops" } */ /* { dg-require-effective-target ilp32 } */ #include <complex.h> -- Summary: pr42427.c:5:21: fatal error: complex.h: No such file or directory Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: danglin at gcc dot gnu dot org GCC build triplet: hppa2.0w-hp-hpux11.11 GCC host triplet: hppa2.0w-hp-hpux11.11 GCC target triplet: hppa2.0w-hp-hpux11.11 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43441
next reply other threads:[~2010-03-19 14:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-19 14:01 danglin at gcc dot gnu dot org [this message] 2010-03-29 2:52 ` [Bug testsuite/43441] " danglin at gcc dot gnu dot org 2010-07-09 22:32 ` danglin at gcc dot gnu dot org
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=bug-43441-276@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).