| 1 |
On Wednesday 25 January 2006 19:49, Stephen P. Becker wrote: |
| 2 |
|
| 3 |
> You aren't serious, are you? Did *you* read the fucking manual *and* |
| 4 |
> comprehend it? Methinks not...upgrading from 3.3 to 3.4 in a |
| 5 |
|
| 6 |
I didn't write the manual, so save your hubris for whoever did. I just |
| 7 |
followed its instructions, I ate the dog food. |
| 8 |
|
| 9 |
> pre-existing install != installing from a fresh stage. First, running |
| 10 |
> bootstrap.sh with the new gcc version unmasked would completely get rid |
| 11 |
> of the "-e system" part of that howto, since that would force your |
| 12 |
> toolchain to rebuild itself. Second, the -e world is to ensure that |
| 13 |
> your full install (which surely has plenty of c++ apps outside of |
| 14 |
> system) is linked against the libstdc++ of the new gcc. |
| 15 |
|
| 16 |
The test has nothing to do with installing from a pre-existing install. The |
| 17 |
test was getting a current gentoo stage tarball with a current portage |
| 18 |
snapshot up to date, stage1 -vs- stage3. Nothing was unmasked either. |
| 19 |
Were you are pulling that from is beyond me. |
| 20 |
|
| 21 |
Running an emerge -e system does not magically switch you over to the new |
| 22 |
gcc, it would uselessly recompile the entire system with gcc 3.3.4 again. |
| 23 |
Hence the need to READ AND COMPREHEND the instructions in the gcc migration |
| 24 |
guide, which was plainly announced in GWN at the time. If you don't |
| 25 |
believe me, go troll around the forums a little and try to help the poor |
| 26 |
saps who didn't realize they needed to follow that guide. Even half of the |
| 27 |
ones who did read the guide completely dorked up their running boxes. |
| 28 |
|
| 29 |
> Remember, in a pristine stage3, system == world. Therefore, your |
| 30 |
> "comparison" is really telling folks to emerge -e system twice in a row. |
| 31 |
> Doing bootstrap.sh followed by 'emerge -e system' from a stage3 is the |
| 32 |
> same thing as doing bootstrap.sh followed by 'emerge -e system' from a |
| 33 |
> stage1...sorry to burst your bubble. So again, idiocy and FUD. |
| 34 |
|
| 35 |
If you actually downloaded a "pristine" stage1 or a stage3 tarball you might |
| 36 |
notice that there are, in fact, packages already present in world. Glibc, |
| 37 |
gettext, nano, gzip, and linux-headers. Not that that matters one iota to |
| 38 |
this conversation, but you need to get your own facts straight before |
| 39 |
running around calling people idiots. |
| 40 |
|
| 41 |
The difference in doing from stage1 instead of stage3 is you don't have to |
| 42 |
go through a gcc migration to prevent your build from being unusable. You |
| 43 |
also go through 1 gcc upgrade (gcc 3.3.5 -> gcc 3.4.4), not 3 (3.3.5 -> |
| 44 |
3.3.6 -> 3.4.4). We are talking reality here, not fantasy. |
Archives