public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10069: -include switch is improperly handled Date: Sat, 15 Mar 2003 21:56:00 -0000 [thread overview] Message-ID: <20030315215600.23511.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10069; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: Sean McNeil <sean@mcneil.com> Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Subject: Re: c++/10069: -include switch is improperly handled Date: Sat, 15 Mar 2003 21:52:02 +0000 Sean McNeil wrote:- > No, I am not using PCH. I'm trying to use the --include switch but it > isn't recognized by C++ as a switch with 2 arguments and so it gets > improperly handled. It ends up reordering my switches and passes -O2 as > the file to include and tries to compile the include file as an input > file. By "C++" do you mean the g++ driver? That may well be a bug. If so, the place to look is cp/lang-specs.h. > So I observed that > > gcc -include hack.h -O2 test.cc > > would end up as > > switches: > -include -O2 > > input files: > hack.h test.cc > > thus it would fail because it cannot find the file "-O2" and because it > would precompile hack.h into hack.pch. LOL. Though if you're not using PCH I don't understand your comment. Neil.
next reply other threads:[~2003-03-15 21:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-15 21:56 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-16 10:26 Neil Booth 2003-03-15 23:56 Sean McNeil 2003-03-15 21:56 Sean McNeil 2003-03-15 21:36 Sean McNeil 2003-03-15 21:36 Neil Booth 2003-03-15 21:26 Neil Booth 2003-03-15 20:26 Sean McNeil 2003-03-15 11:56 Steven Bosscher 2003-03-14 0:06 sean
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=20030315215600.23511.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).