Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!sumax!polari!thebes!camco!bill
From: bill@camco.Celestial.COM (Bill Campbell)
Newsgroups: comp.lang.perl
Subject: Re: Configure: /usr/include
Message-ID: <242@camco.Celestial.COM>
Date: 24 Oct 90 15:09:53 GMT
References: <1990Oct22.082228.6230@robobar.co.uk> <10064@jpl-devvax.JPL.NASA.GOV>
Organization: Celestial Software, Mercer Island, WA
Lines: 22

In article <10064@jpl-devvax.JPL.NASA.GOV> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes:
>In article <1990Oct22.082228.6230@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>: At release of 4.0, would it be reasonable to make "/usr/include" a variable
>: that can be easily changed (e.g.
>: 	sh Configure INCLUDE=/usr/local/lib/gcc-include
>: or something like that ?)  Some of us prefer to leave the vendor's include
>: files alone, but hack the ones we actually use to get the behaviour we want :-)
>
This is really rather easy.  Just add -I$(LOCINCLUDES) to your
CFLAGS where LOCINCLUDES is either an environment variable or
defined in your makefile and points to your local include
directory.

I use this on my Xenix system so that I can have a version of the
SCO supplied headers properly wrapped and debugged and don't have
to work too hard when a new release comes out to fix it.

Bill.
-- 
INTERNET:  bill@Celestial.COM   Bill Campbell; Celestial Software
UUCP:   ...!thebes!camco!bill   6641 East Mercer Way
             uunet!camco!bill   Mercer Island, WA 98040; (206) 947-5591