public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: zack@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/8505: cross cpp0 use PREFIX_INCLUDE_DIR=$prefix/include Date: Fri, 04 Apr 2003 01:06:00 -0000 [thread overview] Message-ID: <20030404010601.18100.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/8505; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: benoit.poulot-cazajou@jaluna.com, stephane.carbillet@jaluna.com, drow@mvista.com Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: preprocessor/8505: cross cpp0 use PREFIX_INCLUDE_DIR=$prefix/include Date: Thu, 03 Apr 2003 17:05:20 -0800 [http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8505] My apologies for letting this go for so long. I am not expert in the domain of cross compilers, and I can think of plausible reasons both to have the PREFIX_INCLUDE_DIR searched and not to have it searched. It would be consistent with what is done for other directories, like LOCAL_INCLUDE_DIR, not to search it; however, it appears that this directory has been searched in cross compilers since forever, so people might be depending on the existing behavior. I would appreciate opinions. Dan, I'm cc:ing you because you've had your fingers in this area recently. zw
next reply other threads:[~2003-04-04 1:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-04 1:06 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-07 16:16 Zack Weinberg 2003-04-07 16:07 zack 2003-04-07 13:16 Daniel Jacobowitz 2002-11-08 15:29 neil 2002-11-08 6:46 stephane.carbillet
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=20030404010601.18100.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=zack@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).