From owner-freebsd-ports@FreeBSD.ORG Wed Nov 6 15:25:56 2013 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F2F508B4 for ; Wed, 6 Nov 2013 15:25:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7A82702 for ; Wed, 6 Nov 2013 15:25:55 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA26372; Wed, 06 Nov 2013 17:25:52 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Ve4zQ-000F8l-G7; Wed, 06 Nov 2013 17:25:52 +0200 Message-ID: <527A5F5B.4040800@FreeBSD.org> Date: Wed, 06 Nov 2013 17:25:15 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Charles Swiger Subject: Re: CC, CPP etc vs CONFIGURE_ENV References: <527A51DF.9090507@FreeBSD.org> <88C65D6E-B4B1-4524-A588-276AADAE2342@mac.com> In-Reply-To: <88C65D6E-B4B1-4524-A588-276AADAE2342@mac.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 15:25:57 -0000 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 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