public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Fitzgibbon <awf@robots.ox.ac.uk>
To: egcs@cygnus.com
Subject: Re: local_prefix a mistake
Date: Tue, 16 Dec 1997 08:45:00 -0000	[thread overview]
Message-ID: <199712161640.QAA01830@gertrude.robots.ox.ac.uk> (raw)
In-Reply-To: <19971215094050.30587@sco.com>

J. Kean Johnston writes:
>On Mon, Dec 15, 1997 at 11:37:48AM +0000, Andrew Fitzgibbon wrote:
>> It's a problem with local_prefix, which ought to be removed.  It's
>> undeniably useful, but the user should explicitly specify any -I flags
>> other than for /usr/include.

>Not when the compiler is installed in /usr/local it shouldn't. The current
>behaviour is correct and desirable. /usr/local is traditionally for add-on
>stuff. You added on a vital VITAL development tool, your compiler. Why
>would one assume if you are brave enough to use a replacement compiler
>that you dont want to use replacement and addon libraries too?

In that case, one should be allowed to specify local-prefix.  In fact, I
used to patch gcc so that multiple -local-prefix options could be supplied
but I stopped when I realised that even the default one was a bad idea.

Any Makefiles that depend on it will not work with other compilers.

>If you REALLY wanna get around this, configure your egcs with --prefix=/usr
>so that everything gets installed in /usr/bin, /usr/include etc. *THAT* is
>when adding -I/usr/local/include would be The Wrong Thing.

Therefore on linux the current behaviour is incorrect and (arguably)
undesirable.

      reply	other threads:[~1997-12-16  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-13 14:41 mutt: slight problem Jean-Pierre Radley
1997-12-14 11:32 ` Robert Lipe
1997-12-14 19:41   ` Jean-Pierre Radley
1997-12-14 20:14   ` Jean-Pierre Radley
1997-12-14 21:22     ` "helpful" include additions, was: " Robert Lipe
1997-12-15  3:41     ` local_prefix a mistake Andrew Fitzgibbon
1997-12-15  7:49       ` H.J. Lu
1997-12-15 11:43         ` Jean-Pierre Radley
1997-12-15  9:38       ` J. Kean Johnston
1997-12-16  8:45         ` Andrew Fitzgibbon [this message]

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=199712161640.QAA01830@gertrude.robots.ox.ac.uk \
    --to=awf@robots.ox.ac.uk \
    --cc=egcs@cygnus.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).