public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "neil at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/11839] [3.4 Regression] GCC cannot find t/t.h if t is a file and t/t.h is in subdirectory temp Date: Sat, 09 Aug 2003 08:55:00 -0000 [thread overview] Message-ID: <20030809085555.32143.qmail@sources.redhat.com> (raw) In-Reply-To: <20030807000409.11839.pinskia@gcc.gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11839 neil at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From neil at gcc dot gnu dot org 2003-08-09 08:55 ------- Fixed.
next prev parent reply other threads:[~2003-08-09 8:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030807000409.11839.pinskia@gcc.gnu.org> 2003-08-09 8:53 ` cvs-commit at gcc dot gnu dot org 2003-08-09 8:55 ` neil at gcc dot gnu dot org [this message] 2003-08-07 0:04 [Bug preprocessor/11839] New: " pinskia at physics dot uc dot edu 2003-08-07 0:06 ` [Bug preprocessor/11839] " pinskia at physics dot uc dot edu 2003-08-07 0:14 ` pinskia at physics dot uc dot edu
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=20030809085555.32143.qmail@sources.redhat.com \ --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).