1 |
Bo Ørsted Andresen ha scritto: |
2 |
> On Thursday 18 January 2007 23:24, b.n. wrote: |
3 |
>> - I'm going to follow [1] (of course) and [2] (looks nice). Other useful |
4 |
>> guides? |
5 |
> |
6 |
> [1] alone should be fine. Assuming your CHOST isn't i386. |
7 |
|
8 |
Sorry for lack of info. I'm running x86 stable, chost is i686-pc-linux-gnu |
9 |
|
10 |
> You didn't tell us whether you are running stable or ~arch. If you're stable |
11 |
> then certainly not since it's not even ~arch yet. Even if ~arch I don't think |
12 |
> so. |
13 |
|
14 |
OK, perfect. |
15 |
|
16 |
>> - Is it mandatory/highly advisable to recompile also the kernel, or can |
17 |
>> I postpone? In the first case, when it's better to recompile it (before |
18 |
>> all/after all)? |
19 |
> |
20 |
> It's best to do it. I think I'd compile it right before `emerge -e world` and |
21 |
> wait with the reboot till it's all done. That way kernel modules compiled |
22 |
> during world will be built against a kernel that was compiled with the same |
23 |
> compiler. |
24 |
|
25 |
This makes much sense. |
26 |
So: |
27 |
|
28 |
emerge -e system |
29 |
[kernel recompile dance] |
30 |
[reboot] |
31 |
emerge -e world |
32 |
|
33 |
? |
34 |
|
35 |
|
36 |
>> - Do I have to emerge glibc 2.4 first and gcc later, or I can have glibc |
37 |
>> emerged in the emerge -e system? |
38 |
> |
39 |
> Assuming your CHOST isn't i386 it's fine to just let `emerge -e system` do it |
40 |
> when instructed to do that. |
41 |
|
42 |
Ok, thanks. |
43 |
|
44 |
m. |
45 |
-- |
46 |
gentoo-user@g.o mailing list |