CC, CPP etc vs CONFIGURE_ENV

Andriy Gapon avg at FreeBSD.org
Wed Nov 6 15:25:57 UTC 2013


on 06/11/2013 17:11 Charles Swiger said the following:
> Hi--
> 
> On Nov 6, 2013, at 6:27 AM, Andriy Gapon <avg at FreeBSD.org> wrote:
>> I wonder why do-configure target explicitly sets things like CC="${CC}"
>> CPP="${CPP}" etc in configure script environment as opposed to them just being
>> placed into CONFIGURE_ENV.
>> What is the technical reason?
> 
> Setting $CC and such worked with older ./configure which didn't implement $CONFIGURE_ENV.
> It also plays more nicely with things which roll their own ./configure as a shim
> that isn't actually GNU autoconf.

Apologies, you seem to think that CONFIGURE_ENV is an environment variable of
its own.  But, as far as I can see, it is not.  It is a make variable with a
value that expands to "FOO=BAR VAR=VAL ..." and those FOO, VAR, etc are the
environment variables that are to be set in configure's environment:

${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

So, either I didn't understand what you said or what you said is not relevant.


-- 
Andriy Gapon


More information about the freebsd-ports mailing list