Alistair Crooks <agc@pkgsrc.org> wrote:
>On Sat, Feb 03, 2001 at 02:25:56PM -0500, Johnny C. Lam wrote:
>> In light of the recent addition of ${FFLAGS} to ${CONFIGURE_ENV}, I
>> think it's also desirable to add the following variables as well:
>> 
>> 	CPPFLAGS
>> 	CXXFLAGS
>> 
>> as both are also used by GNU configure if they are defined in the
>> environment.  We current define:
>> 
>> 	CFLAGS
>> 	FFLAGS
>> 	LDFLAGS
>> 
>> in ${CONFIGURE_ENV}.  Quite a lot of packages already do:
>> 
>> 	CONFIGURE_ENV+=	CPPFLAGS="${CPPFLAGS}"
>> 
>> and several C++ packages do the same with CXXFLAGS. I'm unsure as to
>> why they aren't part of ${CONFIGURE_ENV} already.  Can anyone recall
>> why?
>
>IIRC, it's to do with picking up the right header files, and linking
>with the correct libs, if you already have an installed package for,
>say (for example, off the top of my head, a known incorrect example),
>ncurses, and are compiling a new version with a changed API.

If there are known packages with problems like this (or otherwise picking
up dependencies they shouldn't be), should we perhaps have a per-package
'NO_CPPFLAGS_IN_CONFIGURE_ENV' which prevents the above from happening?
Or maybe a 'NO_LOCALBASE_INCLUDE_IN_CPPFLAGS'?  i.e. something which allows
most packages to have the default environment, with exceptions just for
known issues...

jdarrow

-- 
John Darrow - Senior Technical Specialist               Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187  Fax:    630/752-5968
Alphapage: 6303160707@alphapage.airtouch.com            Pager:  630/316-0707
Email:     John.P.Darrow@wheaton.edu