[gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[b.n.]

Hi,

Quite late :), I'm going to do my homework, that is the loooong upgrade 
to gcc 3.4.x --> 4.1.x

The subject has been widely discussed, so I've just a couple of 
questions to be super-safe:

- I'm going to follow [1] (of course) and [2] (looks nice). Other useful 
guides?

- 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... :/

- 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)?

- Do I have to emerge glibc 2.4 first and gcc later, or I can have glibc 
emerged in the emerge -e system?

- Any other glitch/tarpit I must be aware of?

[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

Thanks for all!
m.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[b.n.]

Bo Ørsted Andresen ha scritto:
> 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.

Sorry for lack of info. I'm running x86 stable, chost is i686-pc-linux-gnu

> 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.

OK, perfect.

>> - 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.

This makes much sense.
So:

emerge -e system
[kernel recompile dance]
[reboot]
emerge -e world

?


>> - 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.

Ok, thanks.

m.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[Dan Farrell]

On Fri, 19 Jan 2007 00:20:57 +0000
"b.n." <brullonulla@gmail.com> wrote:

> Bo Ørsted Andresen ha scritto:
> > 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.
> 
> Sorry for lack of info. I'm running x86 stable, chost is
> i686-pc-linux-gnu
> 


just follow the guide and you shouldn't have any problems. As long as
you're not i386, like b.n. write, you're not likely to have hiccups.  

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[Alan McKinnon]

On Friday 19 January 2007 00:24, b.n. wrote:
> Hi,
>
> Quite late :), I'm going to do my homework, that is the loooong
> upgrade to gcc 3.4.x --> 4.1.x
>
> The subject has been widely discussed, so I've just a couple of
> questions to be super-safe:
>
> - I'm going to follow [1] (of course) and [2] (looks nice). Other
> useful guides?

Those two cover everything you will need to know in just about all cases

> - 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... :/

Dunno about gcc-4.2, you'll have to look at the gnu roadmap to get a 
hint of when they think it'll move closer to a release

> - 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)?

Not at all necessary. The kernel is a free standing block of C code and 
depends only on itself, so ABI issues with other apps simply don;t 
happen. As long as the kernel and all it's modules were compiled with 
the same compiler you will always be fine. (There are exceptions of 
course but with that rule of thumb you can't go wrong)

> - Do I have to emerge glibc 2.4 first and gcc later, or I can have
> glibc emerged in the emerge -e system?

No, just let glibc get recompile along with everything else in emerge -e 
system. Even if there are some oddities of things still linked against 
older versions after that step, the following emerge -e world fixes all 
that

> - Any other glitch/tarpit I must be aware of?

Make sure any kernel modules you may have that are not in portage also 
get recompiled. If you have something like this you already know all 
about it, so I don;t need to give examples.


alan
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[brullo nulla]

> Dunno about gcc-4.2, you'll have to look at the gnu roadmap to get a
> hint of when they think it'll move closer to a release

OK.

> Not at all necessary. The kernel is a free standing block of C code and
> depends only on itself, so ABI issues with other apps simply don;t
> happen. As long as the kernel and all it's modules were compiled with
> the same compiler you will always be fine. (There are exceptions of
> course but with that rule of thumb you can't go wrong)

Yes, but if I keep my 3.4.x compiled kernel and I recompile modules in
Portage with 4.1, there will be problems, maybe (for example, the
vmmon module of vmware-player). Well, I think I'll recompile. I have
other reasons to do it.

> Make sure any kernel modules you may have that are not in portage also
> get recompiled.

Sure (I shouldn't have). I guess also programs not in portage will
have to be recompiled.

Thanks again,
m.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[Alan McKinnon]

On Friday 19 January 2007 17:10, brullo nulla wrote:
> > Dunno about gcc-4.2, you'll have to look at the gnu roadmap to get
> > a hint of when they think it'll move closer to a release
>
> OK.
>
> > Not at all necessary. The kernel is a free standing block of C code
> > and depends only on itself, so ABI issues with other apps simply
> > don;t happen. As long as the kernel and all it's modules were
> > compiled with the same compiler you will always be fine. (There are
> > exceptions of course but with that rule of thumb you can't go
> > wrong)
>
> Yes, but if I keep my 3.4.x compiled kernel and I recompile modules
> in Portage with 4.1, there will be problems, maybe (for example, the
> vmmon module of vmware-player). Well, I think I'll recompile. I have
> other reasons to do it.


Hmmm, yes that's correct. emerge -e world will recompile vmware-modules, 
which will cause problems as you spotted. Kernel recompile is thus 
warranted

> > Make sure any kernel modules you may have that are not in portage
> > also get recompiled.
>
> Sure (I shouldn't have). I guess also programs not in portage will
> have to be recompiled.

Again, depends what they are. For example, I use e17 as my wm and while 
they technically do have ebuilds, they also might as well not be there 
for all the good they do. I can quite happily emerge -e world and not 
update e17 and everything still works, at least for that specific case.

Other apps might be different. Professional audio stuff comes to mind, 
those apps often include drivers for fancy hardware that isn;t in the 
mainline trees, etc etc

alan

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions

[brullo nulla]

On 1/19/07, Alan McKinnon <alan@linuxholdings.co.za> wrote:
> Hmmm, yes that's correct. emerge -e world will recompile vmware-modules,> which will cause problems as you spotted. Kernel recompile is thus
> warranted

OK, now it's fully clear.

> Other apps might be different. Professional audio stuff comes to mind,

That's exactly my case... I use the self-compiled SVN build of LMMS.

Thanks everyone for help. This weekend I'll go for the build.

m.
-- 
gentoo-user@gentoo.org mailing list