| 1 |
Mikey wrote: |
| 2 |
> On Wednesday 25 January 2006 19:13, Stephen P. Becker wrote: |
| 3 |
> |
| 4 |
>> Ahh, so you were the idiot that ran those tests. Congratulations...you |
| 5 |
>> needlessly did a --emptytree world after you had already done |
| 6 |
>> --emptrytree system in order to bloat your results. |
| 7 |
> |
| 8 |
> RTFM - http://www.gentoo.org/doc/en/gcc-upgrading.xml |
| 9 |
|
| 10 |
You aren't serious, are you? Did *you* read the fucking manual *and* |
| 11 |
comprehend it? Methinks not...upgrading from 3.3 to 3.4 in a |
| 12 |
pre-existing install != installing from a fresh stage. First, running |
| 13 |
bootstrap.sh with the new gcc version unmasked would completely get rid |
| 14 |
of the "-e system" part of that howto, since that would force your |
| 15 |
toolchain to rebuild itself. Second, the -e world is to ensure that |
| 16 |
your full install (which surely has plenty of c++ apps outside of |
| 17 |
system) is linked against the libstdc++ of the new gcc. |
| 18 |
|
| 19 |
Remember, in a pristine stage3, system == world. Therefore, your |
| 20 |
"comparison" is really telling folks to emerge -e system twice in a row. |
| 21 |
Doing bootstrap.sh followed by 'emerge -e system' from a stage3 is the |
| 22 |
same thing as doing bootstrap.sh followed by 'emerge -e system' from a |
| 23 |
stage1...sorry to burst your bubble. So again, idiocy and FUD. |
| 24 |
|
| 25 |
-Steve |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives