Subject: Re: Oops.
To: Peter Seebach <email@example.com>
From: Tracy Di Marco White <firstname.lastname@example.org>
Date: 03/03/2003 14:47:07
email@example.com (Peter Seebach) wrote:
>Well, it's finally happened: An install of -current bombed.
> sh build.sh -D /usr/src/dest build > build.log 2>&1
> sh build.sh -D /usr/src/dest install=/ > build.log 2>&1
>This latter failed, and now everything gets
>Shared object "libc.so.12" not found
># cd /lib
># echo libc.*
>libc.so libc.so.12 libc.so.12.88 libc.so.12.89 libc.so.12.91 libc.so.12.95
>Looks like libc.so.12.96 didn't get copied into /lib before the link got
>updated. Copying it in makes everything better.
>Copying set base
>pax: Unable to access ./lib/libc.so.12.95 <No such file or directory>
>pax: Unable to access ./usr/lib/libc.so.12.95 <No such file or directory>
>Thanks especially for /rescue, which got me through this difficult period. :)
>Seems to me that perhaps, during an install like this, symlinks should only
>be updated if the new target already exists?
I ran into this too. The problem is that shlib_version was bumped,
but the set list wasn't changed so the library was built but it