On Wed, Nov 6, 2013 at 6:51 PM, Charles Swiger wrote:
> On Nov 6, 2013, at 7:25 AM, Andriy Gapon wrote:
>>> 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
>>>
On Nov 6, 2013, at 7:25 AM, Andriy Gapon wrote:
>> 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
on 06/11/2013 17:11 Charles Swiger said the following:
> Hi--
>
> On Nov 6, 2013, at 6:27 AM, Andriy Gapon 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 CONFIGU
Hi--
On Nov 6, 2013, at 6:27 AM, Andriy Gapon 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
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?
--
Andriy Gapon
___
freebsd-ports@freebsd.org
