1 |
On Wed, 2006-01-25 at 22:09 +0100, Sven Köhler wrote: |
2 |
> >> I'd like to see, that bootstrap.sh unmerges any old gcc |
3 |
> >> (emerge -C \<${gcc package that we just compiled}) |
4 |
> >> so that a clean system is built with gcc 3.4 only! |
5 |
> > |
6 |
> > Nope. We don't want to remove that choice from the user. We are |
7 |
> > working now towards the 2006.0 release, which means GCC 3.3 will not be |
8 |
> > present in the stage1 tarball. Basically, wait for 2006.0, or follow |
9 |
> > the standard steps to switch compilers yourself. It's not like we're |
10 |
> > forcing you to keep both compilers. ;] |
11 |
> |
12 |
> As i wrote in my other post: |
13 |
> there is no choice! boostrap.sh does what it does: |
14 |
> - installs gcc 3.4 |
15 |
|
16 |
Only because it is unmasked. You could always mask 3.4 to keep it from |
17 |
installing. Yes, this is your choice. |
18 |
|
19 |
> - leaves the gcc 3.3 from the stage1 tarball unchanged |
20 |
|
21 |
You could also remove 3.3 after doing your bootstrap. Remember that |
22 |
part in the Handbook that says you really shouldn't be playing around |
23 |
with bootstrap if you don't know what you're doing and willing to do |
24 |
work on your own system? Here's a prime example. |
25 |
|
26 |
> So actually the first packages compiled by "emerge -e system" are |
27 |
> compiled with the gcc 3.3 which came with the stage1 tarball. |
28 |
|
29 |
Again, this is completely because of you not making any changes on your |
30 |
system. |
31 |
|
32 |
> And that "emerge -e system" updates gcc 3.3 - well, that is only a |
33 |
> side-effect of other things! |
34 |
|
35 |
Which you won't have to deal with for long, 2006.0 is being worked on as |
36 |
we speak. The basic jist of this is that what you are seeing is pretty |
37 |
much expected behavior for bootstrapping using a stage with an older |
38 |
GCC. |
39 |
|
40 |
-- |
41 |
Chris Gianelloni |
42 |
Release Engineering - Strategic Lead |
43 |
x86 Architecture Team |
44 |
Games - Developer |
45 |
Gentoo Linux |