On Thursday 18 January 2007 23:24, b.n. wrote: > - I'm going to follow [1] (of course) and [2] (looks nice). Other useful > guides?
[1] alone should be fine. Assuming your CHOST isn't i386. > - Is there a new incompatible GCC upgrade going to be unmasked? I see > 4.2 and 4.3 are hard masked, but if there is the suspicion they're going > to be used relatively soon AND they are not binary compatible with 4.1, > I may wait for those. When I did 3.3-->3.4, I waited long, and 4.1 > became stable after a week... :/ You didn't tell us whether you are running stable or ~arch. If you're stable then certainly not since it's not even ~arch yet. Even if ~arch I don't think so. > - Is it mandatory/highly advisable to recompile also the kernel, or can > I postpone? In the first case, when it's better to recompile it (before > all/after all)? It's best to do it. I think I'd compile it right before `emerge -e world` and wait with the reboot till it's all done. That way kernel modules compiled during world will be built against a kernel that was compiled with the same compiler. > - Do I have to emerge glibc 2.4 first and gcc later, or I can have glibc > emerged in the emerge -e system? Assuming your CHOST isn't i386 it's fine to just let `emerge -e system` do it when instructed to do that. > - Any other glitch/tarpit I must be aware of? If on the other hand your CHOST is i386 then you must follow the guide for changing your CHOST very carefully (I'd do it first) and avoid the gcc upgrade guide till after you've finished the CHOST guide. If you try to follow both guides at once your system will become broken! (If you want to just stay on i386 then you need a no-nptl profile). > [1]http://www.gentoo.org/doc/en/gcc-upgrading.xml#doc_chap2 > [2]http://www.benr75.com/pages/gentoo_gcc_4.1.1_upgrade_guide -- Bo Andresen
pgp8Ts0y72SCw.pgp
Description: PGP signature
