Re: [gentoo-alt] We need to empty the CONFIG_SITE envvar

[Michael Haubenwallner]

On 10/03/2013 12:59 PM, Fabian Groffen wrote:
> On 03-10-2013 12:16:45 +0200, Michael Haubenwallner wrote:
>> Hi!
>>
>> As I'm still not in sync with vanilla Prefix yet, thought to share this
>> info before you start digging...
>>
>> 've just learned that autoconf's configure may listen to CONFIG_SITE
>> environment variable, and simply sources the file from its value.
>>
>> This has bitten me on openSUSE 12.3 (64bit), where I've wondered why
>> I got configure to use libdir=$prefix/lib64 and libexecdir=$prefix/lib
>> even with some 32bit-only Prefix - and indeed, openSUSE 12.3 does
>> set CONFIG_SITE in /etc/profile.d/site.sh.
>>
>> For Prefix we should have our etc/profile to punt CONFIG_SITE value -
>> either unset directly or set to empty somewhere in etc/profile.d/.
Actually meant etc/env.d/ here.
>>
>> Different thoughts?
>
> Can't we just blacklist it in startprefix?  How does it end up in the
> env anyway?  Is it during bootstrap? then just blacklist it in
> bootstrap-prefix.sh

Anyone starting with the host's loginshell environment does have it set.

For automation purposes it is necessary to be able to run the Prefix environment
simply by "source EPREFIX/etc/profile", so actually one shell's env cumulates:
  source /etc/profile
  source @GENTOO_PORTAGE_EPREFIX@/etc/profile # portage builtin
  source $EPREFIX/etc/profile # envvar with prefix-chaining (like cross-prefix)

Building some non ebuild-ified but autotoolized application using this env setup
will see CONFIG_PATH and fail.

> I'm probably missing something here.  It feels like the PKG_CONFIG_PATH
> thing a bit.

Indeed, they're on the same level. And here I find PKG_CONFIG_PATH being set in both
@GENTOO_PORTAGE_EPREFIX@'s and $EPREFIX's etc/env.d/00basic, unsure if we (still) do
that in vanilla Prefix.

/haubi/