public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Zack Weinberg <zack@codesourcery.com>,
	eggert@twinsun.com, haible@ilog.fr, bug-gnu-gettext@gnu.org,
	bug-textutils@gnu.org, gcc@gcc.gnu.org, meyering@lucent.com,
	nathan@codesourcery.com
Subject: Re: gcc 3.2's cpp breaks configure scripts
Date: Sat, 03 Aug 2002 21:58:00 -0000	[thread overview]
Message-ID: <20020804045813.GA10428@gnu.org> (raw)
In-Reply-To: <200208040333.g743Xkb2003602@hiauly1.hia.nrc.ca>

I think /usr/local is well established as `a standard hierarchy that
overrides /usr', and so gcc should _definitely_ search /usr/local/include
before /usr/include -- many people depend on this behavior.

If you have a more complex installation that breaks (e.g., multiple local
versions of gcc installed), it's up to you to figure out a way to fix it, not
the great majority of people that use /usr/local only.

-Miles
-- 
P.S.  All information contained in the above letter is false,
      for reasons of military security.

  reply	other threads:[~2002-08-04  4:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200208021635.g72GZDrs008047@hiauly1.hia.nrc.ca>
2002-08-01 14:52 ` H}kan Hjort
2002-08-01 20:09   ` John David Anglin
2002-08-02 11:01   ` Bruno Haible
2002-08-02 12:29     ` John David Anglin
2002-08-02 14:42       ` Paul Eggert
2002-08-03 13:48         ` Nix
2002-08-03 14:55           ` John David Anglin
2002-08-03 15:24             ` Zack Weinberg
2002-08-03 19:34           ` Gareth Pearce
2002-08-03 14:42         ` John David Anglin
2002-08-03 15:36           ` Gabriel Dos Reis
2002-08-03 16:07           ` Zack Weinberg
2002-08-03 20:33             ` John David Anglin
2002-08-03 21:58               ` Miles Bader [this message]
2002-08-03 21:58             ` Daniel Jacobowitz
2002-08-11 10:27 John David Anglin
2002-08-12 14:40 ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2002-08-01 16:54 Gareth Pearce
     [not found] <no.id>
2002-08-01 12:02 ` John David Anglin
2002-08-01  0:15 Gareth Pearce
2002-08-01  0:35 ` Jakub Jelinek
2002-08-01  0:03 Gareth Pearce
2002-08-01  0:07 ` Jakub Jelinek
2002-07-31 23:52 Gareth Pearce
2002-07-31  8:58 Jeff Garzik
2002-07-31  9:07 ` Gareth Pearce
2002-07-31 12:44   ` Joe Buck
2002-08-01 10:32     ` Phil Edwards
2002-08-01 11:15       ` Neil Booth
2002-08-01 12:31         ` Phil Edwards
2002-07-31  9:19 ` Andreas Schwab
2002-07-31  9:39   ` Jeff Garzik
2002-07-31  9:39     ` Jan-Benedict Glaw
2002-07-31  9:54       ` Michael Matz
2002-08-01  9:45         ` Kai Henningsen
2002-08-01 12:40           ` Kevin Handy
2002-08-01  9:45   ` Kai Henningsen
2002-08-01 14:47     ` Joe Buck
2002-08-08 20:39       ` Roger Corman
2002-08-09 12:07         ` Joe Buck

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=20020804045813.GA10428@gnu.org \
    --to=miles@gnu.org \
    --cc=bug-gnu-gettext@gnu.org \
    --cc=bug-textutils@gnu.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=eggert@twinsun.com \
    --cc=gcc@gcc.gnu.org \
    --cc=haible@ilog.fr \
    --cc=meyering@lucent.com \
    --cc=nathan@codesourcery.com \
    --cc=zack@codesourcery.com \
    /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: link
Be 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).