glibc 2.31 unmasked and ready to go? [STABLE ONLY]

[dreamer3]

I just did a emerge sync and have a LOT of packages (more than the usual) that say they're ready to be upgraded including glibc-2.31? Could this be some mistake or is it finally declared stable and working in Gentoo?

This appears to be a big push, just want to make sure it was intentional before I upgrade all my tools. A lot of the latest versions appear to have been unmasked with no "newer" unstable ebuilds to take their places. Makes me wonder.

Code: Select all

Calculating world dependencies ...done!
[ebuild    U ] sys-libs/ncurses-5.3-r1
[ebuild    U ] sys-apps/texinfo-4.3
[ebuild    U ] sys-devel/gcc-3.2.1
[ebuild    U ] sys-devel/autoconf-2.54
[ebuild    U ] sys-apps/bash-2.05b-r3
[ebuild    U ] dev-lang/python-2.2.2
[ebuild    U ] sys-apps/portage-2.0.45-r3
[ebuild    U ] sys-devel/binutils-2.13.90.0.16
[ebuild    U ] sys-libs/glibc-2.3.1-r2
[ebuild    U ] sys-libs/cracklib-2.7-r6
...
[ebuild    U ] sys-apps/e2fsprogs-1.32
[ebuild    U ] sys-apps/util-linux-2.11y
[ebuild    U ] sys-apps/net-tools-1.60-r5
[ebuild    U ] sys-apps/gzip-1.3.3

EDIT (rac): Added [STABLE ONLY] to the title, in yet another attempt to keep posts about systems running unstable out of this thread.

[rac]

It does indeed look to be marked stable on x86. Another couple of interesting notes: this will not compile with GCC <3.2, and it uses the 2.2 SLOT.

[dreamer3]

It does indeed look to be marked stable on x86. Another couple of interesting notes: this will not compile with GCC <3.2, and it uses the 2.2 SLOT.

Well, is it even possible to have two glibc's installed at once? Sounds scary to me. So, as I see it the 2.2 slot makes sense. I checked the daily CVS changlog and can't find any of these packages mentioned... And I just synced up EARLY this morning and they weren't there... now they are, so I'd think they'd have to be in the CVS changelogs (on the gentoo website).

With your GCC 3.2 and up comment are you worried about Gentoo 1.2 users? I would hope that would be locked to <2.3 in the /etc/make.profile/pacakges file. This appears to be the case from looking at /usr/portage/profiles/default-1.0 (which I assume is the 1.2 profile??) which is locked at a certain version of glibc...

I think I'm going to hold off until I'm sure...

Edit: Well, from reading the individual Changlog files from each of the packages one by one they seem to have been intentionally bumped stable (including glibc). I'm not through them all yet, but I'd gather this is the beginning of a big push to get ready for the 1.4 release.

[rac]

is it even possible to have two glibc's installed at once?

Theoretically, I think so, but it sounds scary to me too.

With your GCC 3.2 and up comment are you worried about Gentoo 1.2 users?

It's the first ebuild I've seen that behaves this way, and I'm on the record reassuring people sticking with 2.95 that it would probably be a year before we started seeing software that wouldn't compile with 2.95, so I'm just feeling a little stupid and heading off to round up some crow to eat.

[yokem55]

Well based on what's said in this article, under 64 bit linux on hammer you may HAVE to have 2 glibc's in order to run 32 bit software in the otherwise 64bit environment. So, you will need glibc32 nstalled in addition to glibc64 if you want to run binary only 32-bit programs....seems like a strange fate that linux is heading into territory that used plague the win9x series (and probably will again)....

[dreamer3]

Well based on what's said in this article, under 64 bit linux on hammer you may HAVE to have 2 glibc's in order to run 32 bit software in the otherwise 64bit environment. So, you will need glibc32 nstalled in addition to glibc64 if you want to run binary only 32-bit programs....seems like a strange fate that linux is heading into territory that used plague the win9x series (and probably will again)....

If I recall correctly the problem with the Windows 9x series wasn't so much their "thunking" (32 bit wrappers for 16 bit code) as it was the fact that the 16-bit code was non-reentrant and would hold up other processes trying to get to the same routine. Surely that same scenario wouldn't be true of Linux? I'm hoping it's not an apt comparison.

Now you have me thinking about installing both glibc's (add a 2.3 slot) so that all my currently compiled stuff can run against the old, and all my new stuff against the new... Does anyone know if this is practical or even possible?

[BlackPhoenix]

Mmm...glibc2.3...its been a while since Ive sank my teeth in a major system update... (well, if you don't consider my disapointing QT3.1 update...)

Now now...what should I expect after merging that stuff? Stuff I need to reemerge? Commercial apps that won't work anymore? Is it backward compatible?

Yes, as you may have realised by now, I don't know much about glibc...just that its important and I have to be careful...so I am.

[dreamer3]

Mmm...glibc2.3...its been a while since Ive sank my teeth in a major system update... (well, if you don't consider my disapointing QT3.1 update...)

Now now...what should I expect after merging that stuff? Stuff I need to reemerge? Commercial apps that won't work anymore? Is it backward compatible?

I've decided to emerge all the new stuff except glibc-2.31 and simply watch the forum over the next few days or week and see how it goes. Many a time this has proved the right decision when an update to a major package has been released.

[DarkAurora]

I emerged everything, (including the new glibc) and am happy to report 0 breackages. That is no breakages after going through and using some of my oft-used programs (kde, mozilla, etc.) and playing Civilization 3 under winex for a few hours.

I'm pretty sure I see a little increase in overall responsiveness... and I'm certian I see a performance increase in Civ3, for what it's worth.

[dreamer3]

I emerged everything, (including the new glibc) and am happy to report 0 breackages.

Did you re-emerge your entire system against the new glibc (not sure this is necessary) or just just upgraded what portage wanted you to and now everything works?

[darktux]

I've done emerge -u -p world, and everything is running fine.
BTW, I am now emerging mozilla 1.2.1-r1 (have 1.2.1 installed), and everything seems to be working out fine

[jjares]

I've done emerge -u -p world, and everything is running fine.

Do you have any weird/third party software, like java, opera, codeweavers wine, etc?

[Lovechild]

One small step towards safe ELF binary prelinking in Portage.... W000000T

Go devs..

[darktux]

Mozilla is still emerging, but I'd like to add that gaim-cvs and xchat2-cvs compiled fine

GOOOOOO GENTOO!

[Exci]

I'm gonna try it too

I already broke my system once with glibc2.3 but I don't care

living on the edge (even on my stable system, unstable has 2.3 for ages )

[DarkAurora]

Did you re-emerge your entire system against the new glibc (not sure this is necessary) or just just upgraded what portage wanted you to and now everything works?

I just emerged what it wanted me to, which was: gcc, binutils, glibc, and a host of other things.

Do you have any weird/third party software, like java, opera, codeweavers wine, etc?

Well, I run the binary version of winex as well as the naitive linux port of ID Software's Return to Castle Wolfenstein. Both are closed source and run as well as they ever did.

[Optimus]

I tryed update glibs just now and got nice error in depend stage. I use WOLK 3.8 kernel (based on 2.4.18), and glibs get me error on parsing includes in /lib/modules/2.4.18-wolk.3.8/build, this is simlink to usr/src/{wolk-kernel} )))

I change simlink to gentoo kernel sources dir and all build prefectly just now.

But this is a bug!!! Glibc must not depend from current installed kernel. This is wrong! Glibc must depend from separate installed linux-headers.

Anyone can write bugreport? I cannot, becouse bugzilla not like my e-mail adress ))))) with _ in name )))

[pilla]

I am going to try it in a separate partition, in the same way I changed from 1.2 to 1.4rc1... Good thing about having a large HD, even in a notebook

[alshain]

I've just finished emerging glibc 2.3.1 and gcc 3.2.1 and encountered a couple of problems that might be of interest. I'm running kernel 2.4.20-mjc and after rebood the HID module would no longer load. A bit of a problem if you have USB mouse and keyboard. Turned out it was the mousedev and keybdev modules causing a problem - attempting to modprobe them reported unresolved symbols.

Digging out a USB to keyboard adaptor and recompiling the kernel solved things.

I've just discovered that ALSA no longer works either, reporting unresolved symbols in snd.o. I've just re-emerged this and it still doesn't work.

Andrew

[alshain]

Well that was smart! The reason the keyboard didn't work was because I'd compiled keybdev and mousedev into the kernel but somehow the modules from a previous build were hanging around and got copied into /lib/modules. When I did a depmod linux got very confused!

Andrew

[choward]

I tryed update glibs just now and got nice error in depend stage. I use WOLK 3.8 kernel (based on 2.4.18), and glibs get me error on parsing includes in /lib/modules/2.4.18-wolk.3.8/build, this is simlink to usr/src/{wolk-kernel} )))

I change simlink to gentoo kernel sources dir and all build prefectly just now.

But this is a bug!!! Glibc must not depend from current installed kernel. This is wrong! Glibc must depend from separate installed linux-headers.

That's not true. Building glibc depends on the kernel headers. Once glibc is installed, all programs are supposed to use the glibc headers, _not_ the kernel headers.

[Optimus]

I tryed update glibs just now and got nice error in depend stage. I use WOLK 3.8 kernel (based on 2.4.18), and glibs get me error on parsing includes in /lib/modules/2.4.18-wolk.3.8/build, this is simlink to usr/src/{wolk-kernel} )))

I change simlink to gentoo kernel sources dir and all build prefectly just now.

But this is a bug!!! Glibc must not depend from current installed kernel. This is wrong! Glibc must depend from separate installed linux-headers.

That's not true. Building glibc depends on the kernel headers. Once glibc is installed, all programs are supposed to use the glibc headers, _not_ the kernel headers.

As i understand, if glibc build with headers 2.4.20 kernel, other programs MUST use some headers? If i have gentoo-headers from 2.4.19, and build glibc under 2.4.blahblahblah_not_19, it is wrong way? This is can break my other builds later?

[Evangelion]

Hmmmm, I'm not getting glibc2.3.1. No binutils-2.3.90.0.16 or GCC3.2.1 either. I did do emerge sync. Am I doing something wrong?

<==== Gentoo n00b

[sertsa]

Let emerge -pu world do it all (gcc, glibc, binutils, etc). everything went fine. Not sure how pre-linking works, but is it working now 'cause my KDE is way zippier! Apps are definitely opening way quicker on this old p2-333 w/256MB.

Nice.

[burzmali]

a similar thing is happening here; i rsynced 3 computers, two show update to gcc, glibc, etc, the third does not. i have just tried to rsync the third pc a couple more times to see if that would make a difference and still no gcc or glibc for it. i guess i will just try ti sinc it up with one of the other computers, but why the weird behavior?