ronald@robobar.co.uk (Ronald S H Khoo) (10/22/90)
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 :-) Sometimes, it's the easiest way to "tune" Configure's behaviour :-) While I'm here, Larry: will you be including the (vast) amount of portability wisdom added by the development of perl 3 into a new release of metaconfig at any time ? Thanks for your time... -- ronald@robobar.co.uk +44 81 991 1142 (O) +44 71 229 7741 (H)
lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) (10/23/90)
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 :-)
Might be reasonable. I'll think about it. You'll note I've already put
the user's PATH in front of mine, so I'm trying to be obliging.
: While I'm here, Larry: will you be including the (vast) amount of portability
: wisdom added by the development of perl 3 into a new release of
: metaconfig at any time ?
I'm planning to. (Hoping to?)
Larrybill@camco.Celestial.COM (Bill Campbell) (10/24/90)
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
ronald@robobar.co.uk (Ronald S H Khoo) (10/25/90)
bill@camco.Celestial.COM (Bill Campbell) writes: > This is really rather easy. Just add -I$(LOCINCLUDES) to your > CFLAGS Too late! I want *Configure* to use the a different /usr/include. My gcc is compiled not to touch /usr/include at all -- for a good reason. /usr/include on my system contains System V/386 include files. I almost never use these -- I use a Xenix GCC development system, and only ever produce Xenix binaries to run on my SCO Unix box. I want to produce a purely Xenix perl, so I don't want Configure to look in the SCO Unix include files *at all*. Strange ? -- ronald@robobar.co.uk +44 81 991 1142 (O) +44 71 229 7741 (H)