From owner-freebsd-ports@FreeBSD.ORG Wed Nov 6 20:06:02 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 93540188; Wed, 6 Nov 2013 20:06:02 +0000 (UTC) (envelope-from andrew.w.nosenko@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5A80A2A1E; Wed, 6 Nov 2013 20:06:02 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id as1so18244917iec.41 for ; Wed, 06 Nov 2013 12:06:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8EsCBTDohN69DTRXRDnG83HPy7AkWA0BbopOKhak+ps=; b=ySSPfgvRbva6W3zYwVNqtLGnoHff4pI1yfhdRvicggoG1tLyIZhhT31Rwbzo688idD 8WeBYx6M4V6pL6mUXfAukRvczNoYQyfvEFDKM7gKS8kcjzCF4MNYYVE78OSuiv+B6DCk BhcjV1T6PrUMtPoe2EPpwm3+z56kq+IW1vv8yjD2TkBQsT3ahDAI6BwJr7CGD6s8Oy4I AjNecWG6DckaXXponpPHDUEGJiQU85+YGS/xnh1AIOKSv23dtyztBzL9ZgZsWpLiIW4i Asxs+byxM2gVdTfGvmdwxsMI9KhHOv9HP95w1ItRUDInUqb+D/hxcSaRq3PhW4sko7T2 KgfA== MIME-Version: 1.0 X-Received: by 10.50.4.35 with SMTP id h3mr3805494igh.19.1383768361540; Wed, 06 Nov 2013 12:06:01 -0800 (PST) Received: by 10.64.89.2 with HTTP; Wed, 6 Nov 2013 12:06:01 -0800 (PST) In-Reply-To: <17056F94-B724-4EE1-A724-1B9A833D84F6@mac.com> References: <527A51DF.9090507@FreeBSD.org> <88C65D6E-B4B1-4524-A588-276AADAE2342@mac.com> <527A5F5B.4040800@FreeBSD.org> <17056F94-B724-4EE1-A724-1B9A833D84F6@mac.com> Date: Wed, 6 Nov 2013 22:06:01 +0200 Message-ID: Subject: Re: CC, CPP etc vs CONFIGURE_ENV From: "Andrew W. Nosenko" To: Charles Swiger Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Ports , Andriy Gapon 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 20:06:02 -0000 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 >>> 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} > > 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. > After variable substitution by make, it will become something like export VAR1=FOO VAR2=BAR; ./configure and then executed by shell. So, from configure script point of view, it is the same environment variables. -- Andrew W. Nosenko