| 1 |
MIkey wrote: |
| 2 |
>>>A bug, again, that the stage1 installation method was immune to, |
| 3 |
>> |
| 4 |
>>How come? (I'm not familiar with toolchain.eclass at all.) |
| 5 |
> |
| 6 |
> |
| 7 |
> Because the first pass of the bootstrap, that prepares a working gcc/glibc, |
| 8 |
> uses the bootstrap USE flag and disables all but a few other basic USE |
| 9 |
> flags. There is no previous built in dependency problems once you |
| 10 |
> correctly get past that bootstrap phase. It is already assumed that you |
| 11 |
> are upgrading to the latest toolchain during bootstrap. |
| 12 |
|
| 13 |
How are USE flags related to the operation of toolchain.eclass, |
| 14 |
especially calling `gcc-config`? |
| 15 |
|
| 16 |
>>Aaaargh. You've mentioned "bug reports [...] on upgrading gcc via that |
| 17 |
>>method". Got anything apropriate? |
| 18 |
> |
| 19 |
> |
| 20 |
> Not following you... |
| 21 |
|
| 22 |
You stated that there are some bugreports from users having troubles |
| 23 |
with the upgrade guide, especially when following the quicker method. |
| 24 |
Still waiting for them. |
| 25 |
|
| 26 |
WKR, |
| 27 |
-jkt |
| 28 |
|
| 29 |
-- |
| 30 |
cd /local/pub && more beer > /dev/mouth |
Archives