public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5997: CPLUS_INCLUDE_PATH not working properly Date: Mon, 18 Mar 2002 11:16:00 -0000 [thread overview] Message-ID: <20020318191604.11564.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5997; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: jbakker@rssd.esa.int, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c++/5997: CPLUS_INCLUDE_PATH not working properly Date: Mon, 18 Mar 2002 11:08:42 -0800 On Mon, Mar 18, 2002 at 06:25:00PM +0000, Neil Booth wrote: > > I *think* this goes back 3 years (before my time!) to your change to > cppinit.c 1.5 -> 1.6. Would you have a look at it? We used to put > the paths in the env var before the default paths. Now we do something > that is a little different I think. I'm not seeing any problem at all... could you please tell me what's going wrong in your environment? ~/f $ CPLUS_INCLUDE_PATH=`pwd`/include g++ -c -H main.cc ; echo $? /home/zack/f/include/foo.h 0 ~/f $ CPLUS_INCLUDE_PATH=`pwd`/include g++-3.0 -c -H main.cc ; echo $? . /home/zack/f/include/foo.h 0 ~/f $ CPLUS_INCLUDE_PATH=`pwd`/include ~/src/gcc/b/vanilla/gcc/g++ \ -B ~/src/gcc/b/vanilla/gcc/ -H -c main.cc ; echo $? . /home/zack/f/include/foo.h 0 zw
next reply other threads:[~2002-03-18 19:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-18 11:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-20 10:15 neil 2002-03-20 2:16 Jorgo Bakker 2002-03-19 11:46 Neil Booth 2002-03-19 2:06 Jorgo Bakker 2002-03-19 1:36 Zack Weinberg 2002-03-19 1:16 Jorgo Bakker 2002-03-18 11:36 Neil Booth 2002-03-18 10:26 Neil Booth 2002-03-18 8:16 jbakker
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=20020318191604.11564.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --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).