I have noticed the same thing, it is due to the export
CONFIG_PROTECT=-* instruction that you pass right
before emerging portage. I only see one solution :
you can 'export CONFIG_PROTECT_MASK=/etc/make.conf'
Hope this helps
Jonathan
--- Brett I. Holcomb [EMAIL PROTECTED] a
écrit : Is the
On Fri, 2003-02-21 at 01:36, Brett I.Holcomb wrote:
1. Is my edited /etc/make.conf really used during bootstrap.
2. Is the USE variable used for stage 1?
Sort of.
If you look in the bootstrap script there are (were?) references to
'cleanup', this, I believe, handles the moving around of
This is during stage 1 - I don't set the CONFIG_PROTECT
until AFTER stage 1.
On Fri, 21 Feb 2003 10:26:07 +0100 (CET)
Jonathan Chocron [EMAIL PROTECTED] wrote:
I have noticed the same thing, it is due to the export
CONFIG_PROTECT=-* instruction that you pass right
before emerging portage. I
Thanks. I figured bootstrap would want a solid, known set
of parameters. Now if I can figure out why building stage
1 takes so long!
On 21 Feb 2003 09:27:46 +
Mike Williams [EMAIL PROTECTED] wrote:
On Fri, 2003-02-21 at 01:36, Brett I.Holcomb wrote:
1. Is my edited /etc/make.conf
-- Jonathan Chocron [EMAIL PROTECTED] spake thusly:
I have noticed the same thing, it is due to the export
CONFIG_PROTECT=-* instruction that you pass right
before emerging portage. I only see one solution :
you can 'export CONFIG_PROTECT_MASK=/etc/make.conf'
Hope this helps
Actually,
Thank you, Matt, for the explanation. That clears it up.
My PIII dual 933 is on glibc after 10 hours so maybe
sometime this week it will finish!
On Fri, 21 Feb 2003 06:13:23 -0800
Matt Tucker [EMAIL PROTECTED] wrote:
-- Jonathan Chocron [EMAIL PROTECTED] spake thusly:
I have noticed the
Is the USE variable in /etc/make.conf really used during a bootstrap compile?
I ask because I've noticed that if I edit /etc/make.conf per the
instructions, then do the bootstrap and cat or less /etc/make.conf stage 1 is
building it does not have my changes in it - make.conf.build has them but
