From owner-freebsd-ports@FreeBSD.ORG Wed Nov 6 16:51:24 2013 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1FC9665C; Wed, 6 Nov 2013 16:51:24 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from st11p05mm-asmtp003.mac.com (st11p05mm-asmtpout003.mac.com [17.172.108.248]) by mx1.freebsd.org (Postfix) with ESMTP id EB4EF2CAC; Wed, 6 Nov 2013 16:51:23 +0000 (UTC) Received: from [17.198.13.205] (unknown [17.198.13.205]) by st11p05mm-asmtp003.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0MVU005S9PHBFS10@st11p05mm-asmtp003.mac.com>; Wed, 06 Nov 2013 16:51:13 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-11-06_04:2013-11-06,2013-11-06,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1311060117 Content-type: text/plain; charset=iso-8859-1 MIME-version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: CC, CPP etc vs CONFIGURE_ENV From: Charles Swiger In-reply-to: <527A5F5B.4040800@FreeBSD.org> Date: Wed, 06 Nov 2013 08:51:11 -0800 Content-transfer-encoding: quoted-printable Message-id: <17056F94-B724-4EE1-A724-1B9A833D84F6@mac.com> References: <527A51DF.9090507@FreeBSD.org> <88C65D6E-B4B1-4524-A588-276AADAE2342@mac.com> <527A5F5B.4040800@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1510) 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 16:51:24 -0000 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. >=20 > 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=3DBAR VAR=3DVAL ..." and those FOO, VAR, = etc are the > environment variables that are to be set in configure's environment: >=20 > ${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS} Yes, setup via ports/bsd.options.mk and such (aka configure.mk on some = other platforms). > So, either I didn't understand what you said or what you said is not = relevant. That's fair enough-- I don't always manage to be both comprehensible and = relevant. :-) I seemed to recall that sufficiently modern configure's would look into $CONFIGURE_ENV if you set it via: export ${CONFIGURE_ENV}; ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS} ...instead. But I don't see signs of that in GNU autoconf, so that = might be a non-standard thing. Regards, --=20 -Chuck