public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/55399] pch tests fail on mips-mti-linux-gnu target Date: Tue, 20 Nov 2012 00:32:00 -0000 [thread overview] Message-ID: <bug-55399-4-EJ8U6wRixZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55399-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55399 --- Comment #4 from Steve Ellcey <sje at gcc dot gnu.org> 2012-11-20 00:32:22 UTC --- OK, forget the comment about stdc-predef.h, I was looking in my GCC install area instead of the glibc root area. I do have stdc-predef.h. The failure mode is a refusal to use any precompiled headers. I.e. the first line in the test program (common-1.c from gcc.dg/pch/common-1.c) is '#include "common-1.h"' and if there is a common-1.h.gch but no common-1.h, the program will say it can't find common-1.h. ./common-1.c:1:22: fatal error: common-1.h: No such file or directory #include "common-1.h" ^ compilation terminated.
next prev parent reply other threads:[~2012-11-20 0:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-19 21:36 [Bug pch/55399] New: " sje at gcc dot gnu.org 2012-11-19 22:55 ` [Bug pch/55399] " joseph at codesourcery dot com 2012-11-19 23:53 ` sje at gcc dot gnu.org 2012-11-20 0:16 ` joseph at codesourcery dot com 2012-11-20 0:32 ` sje at gcc dot gnu.org [this message] 2012-11-20 0:44 ` joseph at codesourcery dot com 2012-11-21 21:29 ` sje at gcc dot gnu.org 2012-11-21 21:42 ` sje at gcc dot gnu.org 2015-06-12 11:59 ` jakub at gcc dot gnu.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-55399-4-EJ8U6wRixZ@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).