public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jorgo Bakker <jbakker@rssd.esa.int> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5997: CPLUS_INCLUDE_PATH not working properly Date: Wed, 20 Mar 2002 02:16:00 -0000 [thread overview] Message-ID: <20020320101604.25843.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5997; it has been noted by GNATS. From: Jorgo Bakker <jbakker@rssd.esa.int> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: Zack Weinberg <zack@codesourcery.com>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c++/5997: CPLUS_INCLUDE_PATH not working properly Date: Wed, 20 Mar 2002 11:14:38 +0100 That would do the trick, thanks ;-). You may want to consider either to reimplement the build config for solaris or to redoc CPLUS_INCLUDE_PATH, C_INCLUDE_PATH etc..., as it now is confusing (different behavior) and misleading. Thanks for your help. Jorgo Bakker Neil Booth wrote: > Zack Weinberg wrote:- > > > It is reading the header file you asked it to, but interpreting that > > file as a "system header" - and on sparc-sun-solaris2.x, "system > > headers" get treated as wrapped in an implicit extern "C". > > In that case, would the environment variable that is now documented > in 3.1 and 3.2, "CPATH", work instead? GCC has supported it for a long > time, it just hasn't been documented. It treats its path components as > if specified with -I. > > http://gcc.gnu.org/onlinedocs/cpp/Environment-Variables.html > > Neil.
next reply other threads:[~2002-03-20 10:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-20 2:16 Jorgo Bakker [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-20 10:15 neil 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 11:16 Zack Weinberg 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=20020320101604.25843.qmail@sources.redhat.com \ --to=jbakker@rssd.esa.int \ --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).