Re: [gentoo-user] Critical warning: Do not update GLIBC!
* On Tue, Jan 20, 2004 at 07:59:05 +0100, Jens Mayer wrote: [...] Having to drop NPTL for continuing x86 seems to have caused a lot of trouble for some people, and moving to ~x86 to be able to use NPTL is not really painless, neither. I'm a bit at a loss what's the better solution for me at the moment. JFY: After having completed my regular backups, I dared to upgrade my glibc to 2.3.2-r9, removing NPTL from /etc/make.conf. Everything seems to be fine with my upgraded system, it reboots and did not show any obscurities yet. Having removed NPTL, you can see my actual useflags below. I cut the 'emerge info' output to the points that might be of any importance to someone comparing configuration settings. , [ emerge info ] | | Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.0) | = | System uname: 2.6.0 i686 AMD Athlon(tm) Processor | Gentoo Base System version 1.4.3.10p1 | ACCEPT_KEYWORDS=x86 | CFLAGS=-march=athlon-tbird -O3 -mmmx -m3dnow -pipe | FEATURES=autoaddcvs ccache sandbox | MAKEOPTS=-j2 | USE=3dnow X aalib acl alsa apm arts avi berkdb bonobo cdr crypt cups | dga directfb dvd dvdr encode esd fam fbcon foomaticdb gd gdbm ggi gif | gnome gphoto2 gpm gtk gtk2 gtkhtml guile imap imlib java jpeg kde lcms | libg++ libwww mad maildir mbox mikmod mmx motif mozilla mpeg mysql | ncurses nls oggvorbis opengl oss pam pdflib perl pic png python qt | quicktime readline samba scanner sdl slang spell ssl svga tcltk tcpd | tetex tiff truetype usb videos x86 xml2 xmms xv zlib | ` On a second box (my Sony Vaio laptop), I went the opposite way and upgraded the whole system to ~x86, keeping the NPTL useflag and compiling more than 300 packages. ;) Even though I commented my ~x86-settings in /etc/make.conf with # ask for trouble and FU my lovely system BAR, everything went fine here, too. ;) Of course I had to fix a few things manually, but it was pretty painless compared to what I expected. Once again, I'm astonished of the superb work of the gentoo folks. Thank you! Regards, Jens -- Truly great madness can not be achieved without significant intelligence. -- Henrik Tikkanen -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
I'm setting up a new machine from stage1. I would get this anyway, wouldn't I? Can I avoid it somehow? Regards, Goran Na 1074581945, 2004-01-20 ob 07:59, je Jens Mayer napisal(a): * On Tue, Jan 20, 2004 at 07:43:35 +0100, Spider wrote: fun thing is, nptl will -not- work on x86 only on ~x86 due to dependencies. Known fact and not a bug. NPTL used to work with x86 glibc/gcc, so a few people like me have given it a chance. From my experience, the only problem I had was smbmout freezing from time to time (which seems to be a known bug with NPTL 0.28, refering to some Red Hat bugreport I found aksing google). I can not remember that I had to emerge some ~x86 packages due to get NPTL to run. Having to drop NPTL for continuing x86 seems to have caused a lot of trouble for some people, and moving to ~x86 to be able to use NPTL is not really painless, neither. I'm a bit at a loss what's the better solution for me at the moment. Regards, Jens -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
- Original Message - From: Jens Mayer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 6:36 AM Subject: Re: [gentoo-user] Critical warning: Do not update GLIBC! | * On Mon, Jan 19, 2004 at 20:38:53 -0500, Jerry McBride wrote: | | It seems odd that a few people are having problems with the 232r9 glibc. I | just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a | k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest | gcc... | | After the DEPEND/DEPEND problem[1] with glibc-2.3.2r9 and NPTL I emerged | gcc-3.3.2-r5, trying to solve that problem (which it didn't). | | Now I see NPTL support has been removed from glibc-2.3.2r9, solving | the DEPEND/DEPEND problem. | | My question is this: Will upgrading a NPTLed glibc to a non NPTLed | glibc cause known problems (i. e. with applications that have been | compiled with the NPTLed glibc)? Are there any more users who broke | their system upgrading this way? Is there someone who can tell us a | bit more about it? I had the nptl use flag enabled from the installation days but disabled it yesterday just before I updated glibc since portage was giving depend mismatch errors. Then I updated glibc which is the reason I have to reinstall the entire OS now. Whether the toggling of the use flag is the cause or not I'm not sure but logistically it could be. | Reading the reports from Eric and Dhruba at bugzilla[2] and on this | mailinglist, I'm a bit scared of upgrading to glibc-2.3.2-r9 using | a system set up as mine. | | I'd be very happy for some clarifications. ;) | | Thank you for your warnings in here, Dhruba! I wouldn't have | recognized that issue and probably ran into the same problems. My pleasure. I can't quite believe that I've lost the entire system to a routine package update on the stable tree. As soon as I realised I mailed the list. Strangely, AMD systems seem to be unaffected judging from other messages on this thread. Anyway, I'm stuck on XP until I can find the time to reinstall. Life sucks. Dhruba. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Tue, 20 Jan 2004 11:21:18 - Dhruba Bandopadhyay [EMAIL PROTECTED] wrote: My pleasure. I can't quite believe that I've lost the entire system to a routine package update on the stable tree. As soon as I realised I mailed the list. Strangely, AMD systems seem to be unaffected judging from other messages on this thread. Anyway, I'm stuck on XP until I can find the time to reinstall. Life sucks. Yeah, it sucks. For the moment my firewall box is inaccessible (Intel inside) though it continues to perform its functions well enough. I just have to hope the power doesn't go out. Well, I had planned to move it to a Celeron 400 that I have laying around. I guess this could be the time. -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org Signature key (742B740D) available at pgp.mit.edu pgp0.pgp Description: PGP signature
Re: [gentoo-user] Critical warning: Do not update GLIBC!
works here... On Mon, 2004-01-19 at 22:43, Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list -- Regards, Redeeman () ascii ribbon campaign - against html e-mail /\- against microsoft attachments -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Can't you recompile an old version of glibc if you boot from the liveCD? you might even have to recompile some of the basic stuff like util-linux, etc, but at least it's better than wiping the puter clean... BTW, i'm running a p4 1.3Ghz and everything is just fine after the update to -r9 Brendan On Tue, 2004-01-20 at 05:21, Dhruba Bandopadhyay wrote: - Original Message - From: Jens Mayer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 6:36 AM Subject: Re: [gentoo-user] Critical warning: Do not update GLIBC! | * On Mon, Jan 19, 2004 at 20:38:53 -0500, Jerry McBride wrote: | | It seems odd that a few people are having problems with the 232r9 glibc. I | just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a | k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest | gcc... | | After the DEPEND/DEPEND problem[1] with glibc-2.3.2r9 and NPTL I emerged | gcc-3.3.2-r5, trying to solve that problem (which it didn't). | | Now I see NPTL support has been removed from glibc-2.3.2r9, solving | the DEPEND/DEPEND problem. | | My question is this: Will upgrading a NPTLed glibc to a non NPTLed | glibc cause known problems (i. e. with applications that have been | compiled with the NPTLed glibc)? Are there any more users who broke | their system upgrading this way? Is there someone who can tell us a | bit more about it? I had the nptl use flag enabled from the installation days but disabled it yesterday just before I updated glibc since portage was giving depend mismatch errors. Then I updated glibc which is the reason I have to reinstall the entire OS now. Whether the toggling of the use flag is the cause or not I'm not sure but logistically it could be. | Reading the reports from Eric and Dhruba at bugzilla[2] and on this | mailinglist, I'm a bit scared of upgrading to glibc-2.3.2-r9 using | a system set up as mine. | | I'd be very happy for some clarifications. ;) | | Thank you for your warnings in here, Dhruba! I wouldn't have | recognized that issue and probably ran into the same problems. My pleasure. I can't quite believe that I've lost the entire system to a routine package update on the stable tree. As soon as I realised I mailed the list. Strangely, AMD systems seem to be unaffected judging from other messages on this thread. Anyway, I'm stuck on XP until I can find the time to reinstall. Life sucks. Dhruba. -- [EMAIL PROTECTED] mailing list -- Brendan Sullivan [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Tue, 2004-01-20 at 22:21, Dhruba Bandopadhyay wrote: I can't quite believe that I've lost the entire system to a routine package update on the stable tree. Well, in fairness, one should never upgrade a core library, especially glibc, except as part of a major planned system upgrade. We get so used to Gentoo rocking in most situations that unfortunately it's easy to forget that we can't get away from the tribulations the other distros go through to find a stable gcc+glibc+core+bin+file+libs+... combination. Mucking with any of those things invites a full regression system rebuild at best and a disaster at worst. Use space apps, on the other hand (up to and including GNOME!) are awesome to rebuild if as and when you have a reason to. As soon as I realised I mailed the list. Which is much appreciated by the rest of us - and the strength of the Gentoo community! I'm very sorry that your machine got hosed. Let me know if there's anything I can do to help on rebuild. AfC Sydney -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
I was able to upgrade to this version of glibc with no problems as of yet. On Tue, 2004-01-20 at 10:16, Andrew Cowie wrote: On Tue, 2004-01-20 at 22:21, Dhruba Bandopadhyay wrote: I can't quite believe that I've lost the entire system to a routine package update on the stable tree. Well, in fairness, one should never upgrade a core library, especially glibc, except as part of a major planned system upgrade. We get so used to Gentoo rocking in most situations that unfortunately it's easy to forget that we can't get away from the tribulations the other distros go through to find a stable gcc+glibc+core+bin+file+libs+... combination. Mucking with any of those things invites a full regression system rebuild at best and a disaster at worst. Use space apps, on the other hand (up to and including GNOME!) are awesome to rebuild if as and when you have a reason to. As soon as I realised I mailed the list. Which is much appreciated by the rest of us - and the strength of the Gentoo community! I'm very sorry that your machine got hosed. Let me know if there's anything I can do to help on rebuild. AfC Sydney -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Dhruba Bandopadhyay wrote: - Original Message - From: Jens Mayer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 6:36 AM Subject: Re: [gentoo-user] Critical warning: Do not update GLIBC! | * On Mon, Jan 19, 2004 at 20:38:53 -0500, Jerry McBride wrote: | | It seems odd that a few people are having problems with the 232r9 glibc. I | just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a | k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest | gcc... | | After the DEPEND/DEPEND problem[1] with glibc-2.3.2r9 and NPTL I emerged | gcc-3.3.2-r5, trying to solve that problem (which it didn't). | | Now I see NPTL support has been removed from glibc-2.3.2r9, solving | the DEPEND/DEPEND problem. | | My question is this: Will upgrading a NPTLed glibc to a non NPTLed | glibc cause known problems (i. e. with applications that have been | compiled with the NPTLed glibc)? Are there any more users who broke | their system upgrading this way? Is there someone who can tell us a | bit more about it? I had the nptl use flag enabled from the installation days but disabled it yesterday just before I updated glibc since portage was giving depend mismatch errors. Then I updated glibc which is the reason I have to reinstall the entire OS now. Whether the toggling of the use flag is the cause or not I'm not sure but logistically it could be. | Reading the reports from Eric and Dhruba at bugzilla[2] and on this | mailinglist, I'm a bit scared of upgrading to glibc-2.3.2-r9 using | a system set up as mine. | | I'd be very happy for some clarifications. ;) | | Thank you for your warnings in here, Dhruba! I wouldn't have | recognized that issue and probably ran into the same problems. My pleasure. I can't quite believe that I've lost the entire system to a routine package update on the stable tree. As soon as I realised I mailed the list. Strangely, AMD systems seem to be unaffected judging from other messages on this thread. Anyway, I'm stuck on XP until I can find the time to reinstall. Life sucks. Why can't you ask someone to provide you with a binary package of a *good* glibc? You could then boot from the LiveCD and 'tar -C /mnt/gentoo -xjf glibc-good version.tar.bz2'. I'm not quite sure if this will work, but it certaintly can't hurt if your system if FUBAR already. -- Andrew Gaffney System Administrator Skyline Aeronautics, LLC. 776 North Bell Avenue Chesterfield, MO 63005 636-357-1548 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Andrew Gaffney said: Why can't you ask someone to provide you with a binary package of a *good* glibc? Because it's more dramatic to drop the W word. :-| -Eric -- arctic bears - email and name services 25 email [EMAIL PROTECTED] CA$11.95/month DNS starting at CA$3.49/month - domains from CA$25.95/year for details contact [EMAIL PROTECTED] or visit http://www.arcticbears.com -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Mon, 2004-01-19 at 14:43, Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. After seeing some successes posted to the list, I updated this morning. Haven't rebooted but so far so good: www root # emerge search glibc | grep -A 5 'sys-libs\/glibc' * sys-libs/glibc Latest version available: 2.3.2-r9 Latest version installed: 2.3.2-r9 Size of downloaded files: 14,946 kB Homepage:http://www.gnu.org/software/libc/libc.html Description: GNU libc6 (also called glibc2) C library www root # My system info is below if it would be helpful to anyone thinking of attempting same. -Collin -- ~~ Collin Starkweather, Ph.D. [EMAIL PROTECTED] University of Colorado Department of Economics ~~ www root # emerge --info Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.22-gentoo-r5) = System uname: 2.4.22-gentoo-r5 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS=x86 AUTOCLEAN=yes CFLAGS=-O2 -mcpu=i686 -pipe CHOST=i686-pc-linux-gnu COMPILER=gcc3 CONFIG_PROTECT=/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/alias /var/qmail/control CONFIG_PROTECT_MASK=/etc/gconf /etc/env.d CXXFLAGS=-O2 -mcpu=i686 -pipe DISTDIR=/usr/portage/distfiles FEATURES=autoaddcvs ccache sandbox GENTOO_MIRRORS=http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo; MAKEOPTS=-j2 PKGDIR=/usr/portage/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage PORTDIR_OVERLAY= SYNC=rsync://rsync.namerica.gentoo.org/gentoo-portage USE=X apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib www root # uname -a Linux www 2.4.22-gentoo-r5 #1 Mon Jan 19 12:11:02 GMT 2004 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux www root # emerge search binutils | grep -A 5 'sys-devel\/binutils$' * sys-devel/binutils Latest version available: 2.14.90.0.7-r4 Latest version installed: 2.14.90.0.7-r4 Size of downloaded files: 10,327 kB Homepage:http://sources.redhat.com/binutils/ Description: Tools necessary to build programs www root # -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dhruba Bandopadhyay wrote: | This is just to stop others sharing the misfortune that occurred to me. I | updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage | and also most applications. | | Do NOT perform this update until bug 38619 [1] has been worked out. | | Dhruba. | | [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 /me hits ^C Hey, thanks for the heads-up. What is that ACCEPT_KEYWORDS=~x86 stuff for again? I forget. :) - -- ** * ____ _ * * ___/ /__ ___ / /_(_)__ ___ __ __ ___ __ _ * * / _ / -_)_-/ __/ / _ \/ -_) // // __/ _ \/ ' \ * * \_,_/\__/___/\__/_/_//_/\__/\_, (_)__/\___/_/_/_/ * *(___/ [EMAIL PROTECTED] * ** BOFH Excuse #281: The co-locator cannot verify the frame-relay gateway to the ISDN server. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFADFhmoAq8t3CabwcRAn3bAJ49SSVcg/UohylU8OqaAUP65MkCOgCeKiCE hD3ZX47/QzQMd3FonV8yqbM= =xCqG -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list What if we did!?!?!? I havent rebooted yet so I havent noticed anything funky.. I emerge'd it this morning ;( what should I do? -- http://ka0ttic.dyndns.org/ /usr/bin/fortune says: God grant us the serenity to accept the things we cannot change, courage to change the things we can, and wisdom to know the difference. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Walker wrote: | What if we did!?!?!? | | I havent rebooted yet so I havent noticed anything funky.. I emerge'd it | this morning ;( | | what should I do? Well, if you take advice from the peanut gallery, I'd say don't reboot and wait for the new version. - -- ** * ____ _ * * ___/ /__ ___ / /_(_)__ ___ __ __ ___ __ _ * * / _ / -_)_-/ __/ / _ \/ -_) // // __/ _ \/ ' \ * * \_,_/\__/___/\__/_/_//_/\__/\_, (_)__/\___/_/_/_/ * *(___/ [EMAIL PROTECTED] * ** BOFH Excuse #187: Reformatting Page. Wait... -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFADGXLoAq8t3CabwcRAjgcAKCpEzpAnTXFnthVAYjqVpmyFbUvXQCggBji HCBaZTnvEZc4wFouS3F6hkw= =dOJ9 -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Mon, 2004-01-19 at 15:21, Greg Donald wrote: Dhruba Bandopadhyay wrote: | This is just to stop others sharing the misfortune that occurred to me. I | updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage | and also most applications. | | Do NOT perform this update until bug 38619 [1] has been worked out. Thanks much. I was literally in the src_compile of the emerge. ^S ^C ^Q. -Collin -- ~~ Collin Starkweather, Ph.D. [EMAIL PROTECTED] University of Colorado Department of Economics ~~ -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 Uh oh. Mine just finished a few minutes ago. But, everything seems normal... -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
yeah, thanks...i had JUST started emerging a bunch of stuff (including glibc) and hit ^C *real* quicki've had enough of glibc messing up my linux box =0P On Mon, 2004-01-19 at 16:21, Greg Donald wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dhruba Bandopadhyay wrote: | This is just to stop others sharing the misfortune that occurred to me. I | updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage | and also most applications. | | Do NOT perform this update until bug 38619 [1] has been worked out. | | Dhruba. | | [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 /me hits ^C Hey, thanks for the heads-up. What is that ACCEPT_KEYWORDS=~x86 stuff for again? I forget. :) - -- ** * ____ _ * * ___/ /__ ___ / /_(_)__ ___ __ __ ___ __ _ * * / _ / -_)_-/ __/ / _ \/ -_) // // __/ _ \/ ' \ * * \_,_/\__/___/\__/_/_//_/\__/\_, (_)__/\___/_/_/_/ * *(___/ [EMAIL PROTECTED] * ** BOFH Excuse #281: The co-locator cannot verify the frame-relay gateway to the ISDN server. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFADFhmoAq8t3CabwcRAn3bAJ49SSVcg/UohylU8OqaAUP65MkCOgCeKiCE hD3ZX47/QzQMd3FonV8yqbM= =xCqG -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list -- Brendan Sullivan [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Critical warning: Do not update GLIBC!
This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 Uh oh. Mine just finished a few minutes ago. Sounds terrible, but so far I seem to be OK. I'm running an older kernel - 2.4.22-r2. I did the upgrade early this morning and have built a number of tools since then. No real problems. I did have a semi-big problem yesterday with an emerge of perl continually corrupting a specific file and causing an fsck. I was unable to use many apps for a day without perl. That's fixed now. From that experience I would recommend keeping an older kernel or two around for emergencies. - Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On January 19, 2004 06:48 pm, Mark Knecht wrote: I did have a semi-big problem yesterday with an emerge of perl continually corrupting a specific file and causing an fsck. I was unable to use many apps for a day without perl. That's fixed now. how'd you fix that? i have the exact-same problem. -- i came to america because of the great, great freedom which I heard existed in this country. i made a mistake in selecting america as a land of freedom, a mistake i cannot repair in the balance of my lifetime. - albert Einstein -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Critical warning: Do not update GLIBC!
hmmwell, i dont use really aggressive USE flags or CFLAGSi'll take the plunge and let ya all know how it goesi guess that's what the liveCD is for huh? ;) On Mon, 2004-01-19 at 17:48, Mark Knecht wrote: This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 Uh oh. Mine just finished a few minutes ago. Sounds terrible, but so far I seem to be OK. I'm running an older kernel - 2.4.22-r2. I did the upgrade early this morning and have built a number of tools since then. No real problems. I did have a semi-big problem yesterday with an emerge of perl continually corrupting a specific file and causing an fsck. I was unable to use many apps for a day without perl. That's fixed now. From that experience I would recommend keeping an older kernel or two around for emergencies. - Mark -- [EMAIL PROTECTED] mailing list -- Brendan Sullivan [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Critical warning: Do not update GLIBC!
I did have a semi-big problem yesterday with an emerge of perl continually corrupting a specific file and causing an fsck. I was unable to use many apps for a day without perl. That's fixed now. how'd you fix that? i have the exact-same problem. I had a copy of 2.4.20-r(something) on my system. I booted into that kernel and built perl using it. I then came back to 2.4.22-r2 where I live and things seem to be fine. HTH, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Mon, 19 Jan 2004 17:42:26 -0500 Aaron Walker [EMAIL PROTECTED] wrote: Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list What if we did!?!?!? I havent rebooted yet so I havent noticed anything funky.. I emerge'd it this morning ;( what should I do? I have been running it for a while now on a couple of machines without problem, but something seems to have killed one of my machines after the update. I can only imagine that this is a USE problem. The only other difference between the machines in my case is that the two that made it are both AMD and the one that died is Intel. -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org Signature key (742B740D) available at pgp.mit.edu pgp0.pgp Description: PGP signature
RE: [gentoo-user] Critical warning: Do not update GLIBC!
hmmwell, i dont use really aggressive USE flags or CFLAGSi'll take the plunge and let ya all know how it goesi guess that's what the liveCD is for huh? ;) Brendan, Please keep in mind that I haven't built portage, python or anything real critical. I've been building some DVD tools to look at a single DVD problem in xine. Proceed with care! Cheers, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
El Martes, 20 de Enero de 2004 00:40, Ian Truelsen escribió: I have been running it for a while now on a couple of machines without problem, but something seems to have killed one of my machines after the update. I can only imagine that this is a USE problem. The only other difference between the machines in my case is that the two that made it are both AMD and the one that died is Intel. My AMD without 'nptl' USE flag, and with glibc 2.3.2-r9, run OK too. -- --- Cordiales saludos Manuel Pérez López [EMAIL PROTECTED] http://www.ieduca.net/ --- Muy importante: si usted es usuario/a de OutLook como cliente de correo, debido a la incapacidad de ese programa para detener el envio de virus, le ruego elimine de su lista de direcciones o agenda las posibles referencias a una dirección de correo mía, incluyendo ésta desde la que le escribo. --- Gentoo Linux: Portage 2.0.49 gcc 3.2.3 Linux 2.6.1 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Monday 19 January 2004 04:43 pm, Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list It seems odd that a few people are having problems with the 232r9 glibc. I just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest gcc... This ought to be an interesting development. -- ** Registered Linux User Number 185956 http://groups.google.com/groups?hl=ensafe=offgroup=linux Join me in chat at #linux-users on irc.freenode.net This email account no longers accepts attachments or messages containing html. 7:40pm up 111 days, 33 min, 9 users, load average: 0.00, 0.00, 0.00 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
Works here too on dual AMD 1.9 system. Jerry McBride wrote: On Monday 19 January 2004 04:43 pm, Dhruba Bandopadhyay wrote: Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list It seems odd that a few people are having problems with the 232r9 glibc. I just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest gcc... This ought to be an interesting development. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Tuesday 20 Jan 2004 01:53, Brett I. Holcomb wrote: Works here too on dual AMD 1.9 system. And here, on two KT600 boxes with Athlon XPs, one of which has rebooted without problems. -- == Gentoo Linux: Portage 2.0.49-r20kernel-2.6.1-gentoo-w4l i686 AMD Athlon(tm) XP 3200+KDE: 3.1.5 Qt: 3.2.3 gcc(GCC): 3.2.3 == -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
On Mon, 2004-01-19 at 18:05, Peter Ruskin wrote: On Tuesday 20 Jan 2004 01:53, Brett I. Holcomb wrote: Works here too on dual AMD 1.9 system. And here, on two KT600 boxes with Athlon XPs, one of which has rebooted without problems. Yes, I've run emerge sync and built a bunch of stuff today, redone some devfsd configuration, added scsi emulation to my grub.conf file and rebooted a bunch of times this evening. No problems here so far. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
* On Mon, Jan 19, 2004 at 20:38:53 -0500, Jerry McBride wrote: It seems odd that a few people are having problems with the 232r9 glibc. I just rolled it out on three machines, 1 amdXP, 1 amdMobile an old k6-2 and a k6-3 systems and no errors. All running 2.6.1 kernels, NPTL and the latest gcc... After the DEPEND/DEPEND problem[1] with glibc-2.3.2r9 and NPTL I emerged gcc-3.3.2-r5, trying to solve that problem (which it didn't). Now I see NPTL support has been removed from glibc-2.3.2r9, solving the DEPEND/DEPEND problem. My question is this: Will upgrading a NPTLed glibc to a non NPTLed glibc cause known problems (i. e. with applications that have been compiled with the NPTLed glibc)? Are there any more users who broke their system upgrading this way? Is there someone who can tell us a bit more about it? Reading the reports from Eric and Dhruba at bugzilla[2] and on this mailinglist, I'm a bit scared of upgrading to glibc-2.3.2-r9 using a system set up as mine. I'd be very happy for some clarifications. ;) Thank you for your warnings in here, Dhruba! I wouldn't have recognized that issue and probably ran into the same problems. Regards, Jens Footnotes: -- [1] http://bugs.gentoo.org/show_bug.cgi?id=38622 [2] http://bugs.gentoo.org/show_bug.cgi?id=38619 PS: Wouldn't it have been a considerable solution to have the glibc ebuild correctly recognize a decent gcc (like 3.3.2-r5), maybe issuing some warnings while emerging with NPTL, or are there other (technical) reasons not to do this? -- The discerning person is always at a disadvantage. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Critical warning: Do not update GLIBC!
begin quote On Tue, 20 Jan 2004 01:11:33 +0100 Manuel Pérez López [EMAIL PROTECTED] wrote: My AMD without 'nptl' USE flag, and with glibc 2.3.2-r9, run OK too. fun thing is, nptl will -not- work on x86 only on ~x86 due to dependencies. Known fact and not a bug. //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end pgp0.pgp Description: PGP signature
[gentoo-user] Critical warning: Do not update GLIBC!
Hello This is just to stop others sharing the misfortune that occurred to me. I updated glibc to 2.3.2-r9 on stable x86 tree and it broke python, portage and also most applications. Do NOT perform this update until bug 38619 [1] has been worked out. Dhruba. [1] http://bugs.gentoo.org/show_bug.cgi?id=38619 -- [EMAIL PROTECTED] mailing list
