This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: /usr/local/include before /usr/include?
- To: Brian Ford <ford at vss dot fsi dot com>
- Subject: Re: /usr/local/include before /usr/include?
- From: David Starner <dvdeug at x8b4e53cd dot dhcp dot okstate dot edu>
- Date: Fri, 25 Feb 2000 12:53:07 -0600
- Cc: gcc at gcc dot gnu dot org
- References: <Pine.GSO.4.21.0002251206090.24389-100000@eos>
- Reply-To: dstarner98 at aasaa dot ofe dot org
On Fri, Feb 25, 2000 at 12:08:13PM -0600, Brian Ford wrote:
> I just noticed that gcc seems to default to having /usr/local/include
> before /usr/include in its include path. Why is this?
>
> Should not all system includes have first priority unless someone
> specifically asks for something different?
Aren't /usr/local/include files system includes? If a system
administrator, for whatever reason, wants to override a
system include, should he not put it in /usr/local/include?
(Should the system administrator override a system
include under normal circumstances? No. But if she creates
/usr/local/include/stdio.h, I would assume that's what she
intended to do.)
--
David Starner - dstarner98@aasaa.ofe.org
Only a nerd would worry about wrong parentheses with
square brackets. But that's what mathematicians are.
-- Dr. Burchard, math professor at OSU