Subject: Re: current libc failure
To: Martin Husemann <martin@duskware.de>
From: Nigel Reed <nigel@nelgin.nu>
List: current-users
Date: 06/22/2001 11:22:20
I build a system yesterday from -current (upped from 1.5.1_BETA2) and
my libc appears to be finehere.

-r--r--r--  1 root  wheel  1286630 Jun 21 22:00 libc.a
lrwxr-xr-x  1 root  wheel       13 Jun 21 22:00 libc.so -> libc.so.12.76
lrwxr-xr-x  1 root  wheel       13 Jun 21 22:00 libc.so.12 -> libc.so.12.76

You don't mention if your libc was 12.76 or not.

Regards
Nigel

On Fri, Jun 22, 2001 at 05:20:32PM +0200, Martin Husemann wrote:
> Hi!
> 
> I'm not yet sure if this affects all ports, I noticed on sparc64 and 
> investigation didn't reveal anything real yet.
> 
> I did a cvs update a few hours ago, booted new kernel and build a new libc.
> 
> After installing libc, *many* programs start to fail, including: su, getty,
> gdb, ktrace and who.
> 
> Removing the libc symlink and pointing it to an older version (libc.so.12.75)
> made everything happy again.
> 
> So, folks, be carefull when upgrading right now; and better keep a root shell
> around.
> 
> 
> Martin

--