GCC 4.1.1 and glibc 2.4 going stable!

[loki99]

As you can guess by the title, the Gentoo base project has announced that sys-devel/gcc-4.1.1 and sys-libs/glibc-2.4-r3 will be going stable on both amd64 and x86 this week because of their use in the upcoming 2006.1 release.

This also marks a major upgrade of the GNU Compiler Collection (GCC) to version 4.1.1 on Gentoo. This upgrade requires the user to perform certain tasks outlined in the GCC Upgrading Guide, which has recently been updated with information on GCC 4.1.1 for Gentoo users.

Users who do not wish to upgrade to GCC 4.1.1 will require a few more steps to ensure their systems are not upgraded.

I wonder how many people will update their GCC without checking the docs, just to complain that the devs broke his/her box.

[hielvc]

Yaa then they'll bitch at their User Rep to protect them from such high handed actions

[Q-collective]

Yeah right

[mark_alec]

I would like to thank those that have worked on porting all (hopefully) the packages in the tree to a version compatible with GCC 4.1. I hope the upgrade goes as smoothly for me as the 3.3 3.4 one went.

[Paapaa]

Great job and thanks to all developers involved! Nice to get Gentoo to modern 4.1. age.

[Pablo_Escobar]

I'm anxious to see it coming stable in the portage.
GWN said "this week", not much of it left

[chicha]

Hello all !

I have a little question and maybe some of you could help about this :

In the General Upgrade Instructions section (the appropriate section for migrating from gcc-3.4 to gcc-4.1 or greater) it is mentionned to rebuild the libtool. Ok for me. But it is also advised to rebuild system and world to "make use of the new compiler".
Why rebuild system and world in this case ? Is it just to benefit from gcc-4 new features or is it REALLY IMPORTANT to maintain the stability of my whole system ?

also can a library compiled with gcc-4 still be used by a software compiled with gcc-3.4 ?

Thank you very much for your help !
Cheers,

Chicha.

[Voltago]

I wonder how many people will update their GCC without checking the docs, just to complain that the devs broke his/her box.

Well, maybe the devs should add a new option to portage for important upgrades like this. I'm thinking of something along the lines of

Code: Select all

emerge -u --ireallyreallyreadthedocsandknowthatthisupdatewillbreakmymachineandciaranmwillbeatmeupifididnt world

[swimmer]

Wouldn't it be nice if the GCC Upgrading Guide would take account of the new GCC 4.1.1?

I'm sure that the steps are the same but it would read and look nicer to the people who get there for the first time ...

Just a thought
swimmer

[Paapaa]

Wouldn't it be nice if the GCC Upgrading Guide would take account of the new GCC 4.1.1?

Did you notice this red box:

It should be noted that upgrading from GCC-3.4 to GCC-4.1 or greater still requires you to follow the general upgrading instructions, as GCC-3.4 and GCC-4.1 use slightly different ABIs.

The question is not if something is mentioned, the question is how big font, how ugly colors and how much blinking should be used so the users actually read it (At least I think the above is clear enough.)

[swimmer]

Please don't blame me!

Of course I noticed the red box and I read it - it was more the feeling that this was the *only* place where 4.1 is mentioned. *I* would find it helpful if there is a dedicated section for the upgrade from 3.4 to 4.1 ... it just looks better and helps the people who are not so sure how to work out this upgrade when they come to this site.

But if you want to make fun of it go on ...

Greetz
swimmer

[loki99]

I wonder how many people will update their GCC without checking the docs, just to complain that the devs broke his/her box.

Well, maybe the devs should add a new option to portage for important upgrades like this. I'm thinking of something along the lines of

Code: Select all

emerge -u --ireallyreallyreadthedocsandknowthatthisupdatewillbreakmymachineandciaranmwillbeatmeupifididnt world

You are right. Something like that is definately needed and it is being worked on, as far as I know. At least there is a Glep for it and it just has been discussed in the july council meeting. Here are the logs if you are interested.

But since one has to actively switch to the new GCC, I hope this one will not be that much of a hassel.

"If you install a newer version of GCC, the system will not switch over to use it automatically. You'll have to explicitly request the change because the migration process might require some additional steps. If you decide not to switch, Portage will continue to use older version of your compiler until you change your mind, or remove the old compiler from the system."

[Paapaa]

Of course I noticed the red box and I read it - it was more the feeling that this was the *only* place where 4.1 is mentioned. *I* would find it helpful if there is a dedicated section for the upgrade from 3.4 to 4.1 ... it just looks better and helps the people who are not so sure how to work out this upgrade when they come to this site.

First they clearly tell (in the red box) that if you update from 3.4 to 4.1 you need to follow the general upgrading instructions. And below that there are the general upgrading instructions. Having yet another identical section dedicated to 3.4 to 4.1 serves no purpose IMO. And I think a red box with "Warning" is as clear as it gets. But yes, that is just my opinion.

[anello]

Does anybody know when exactly this gcc upgrade will be available into portage? Cause I'm just about to add one gentoo system to productive environment and I want to upgrade it before I'll do that, but need to give my associates some kind of schedule.

[loki99]

Does anybody know when exactly this gcc upgrade will be available into portage?

It is already; you just have to unmask it in your keywords.

[anello]

It is already; you just have to unmask it in your keywords.

Yeah, you're completly right! But that's not the point, I'd just like to know.

PS: I think I have to rephrase my question ... Does anybody know when exactly this gcc upgrade will be available into STABLE?

[RoundsToZero]

Wouldn't it be nice if the GCC Upgrading Guide would take account of the new GCC 4.1.1?

Did you notice this red box:

It should be noted that upgrading from GCC-3.4 to GCC-4.1 or greater still requires you to follow the general upgrading instructions, as GCC-3.4 and GCC-4.1 use slightly different ABIs.

The question is not if something is mentioned, the question is how big font, how ugly colors and how much blinking should be used so the users actually read it (At least I think the above is clear enough.)

So does that mean I still revdep-rebuild against libstdc++.so.5, or do I now revdep-rebuild against libstdc++.so.6? The red box says follow the general instructions, which include "emerge -eav system" and "emerge -eav world" for the purpose of "[making] use of the new compiler." I don't want to recompile everything just for the heck of it, I just want to make sure things don't break. Previously that just meant C++ stuff. I found some references to libstdc++.so.7, but I'm not sure if that's part of GCC 4.1 or not.

[Paapaa]

So does that mean I still revdep-rebuild against libstdc++.so.5, or do I now revdep-rebuild against libstdc++.so.6? The red box says follow the general instructions, which include "emerge -eav system" and "emerge -eav world" for the purpose of "[making] use of the new compiler." I don't want to recompile everything just for the heck of it, I just want to make sure things don't break. Previously that just meant C++ stuff. I found some references to libstdc++.so.7, but I'm not sure if that's part of GCC 4.1 or not.

Well, according to the guide you should do as told in section 2 - if upgrading from 3.4 to 4.1. I trust that you really must compile everything (first system and then world).

[Carlo]

Why rebuild system and world in this case ? Is it just to benefit from gcc-4 new features or is it REALLY IMPORTANT to maintain the stability of my whole system ?

When the GCC guys change the ABI and you want to switch to the new compiler, you have to rebuild your whole system. There is no way around it. Trying to build some application using libraries built with compilers having a different ABI results in build errors. So yes, it's R E A L L Y IMPORTANT.

So does that mean I still revdep-rebuild against libstdc++.so.5, or do I now revdep-rebuild against libstdc++.so.6?

That was the fix for the C++ ABI change from GCC 3.3 from 3.4. No, this is not the way to update to GCC 4.1.1

[forkboy]

I've read/heard/been told that to upgrade properly you need to

Code: Select all

emerge -e system
emerge -e system
emerge -e world
emerge -e world

Is this really necessary? Or will it be fine to just follow the guide?

[playfool]

I've read/heard/been told that to upgrade properly you need to

Code: Select all

emerge -e system
emerge -e system
emerge -e world
emerge -e world

Is this really necessary? Or will it be fine to just follow the guide?

The guide is in place for a reason

[Paapaa]

I've read/heard/been told that to upgrade properly you need to

Code: Select all

emerge -e system
emerge -e system
emerge -e world
emerge -e world

Is this really necessary? Or will it be fine to just follow the guide?

This is exactly the reason why I think Portage should handle all this. The user shouldn't need to know/worry about when to recompile and what to recompile and in what order etc.

[Dralnu]

I skipped a good porition of the thread, but wanted to chim in with this:

Unless Portage updates your version of GCC automatically (which I doubt), you'll probably get 4.1.1, and then keep using the old 3.4.x gcc version unless you run gcc-config.

edit:
I know this because I upgraded to gcc-4.1.1 not a week ago (ironic, isn't it? lol)

[chicha]

When the GCC guys change the ABI and you want to switch to the new compiler, you have to rebuild your whole system. There is no way around it. Trying to build some application using libraries built with compilers having a different ABI results in build errors. So yes, it's R E A L L Y IMPORTANT.

Thank you very much Carlo ! This is exactly the info I needed !
Cheers,

Chicha

[jamapii]

It should be noted that upgrading from GCC-3.4 to GCC-4.1 or greater still requires you to follow the general upgrading instructions, as GCC-3.4 and GCC-4.1 use slightly different ABIs.

I'm looking for information about these ABI changes, but can't find any (only about MIPS and SPARC in 3.3 -> 3.4). Does anyone have a link?