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

Reply via email to