On Sat, Nov 25, 2000 at 02:44:08AM -0600, Bill Fumerola wrote:
> On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote:
> > On a fresh hard drive I installed 5.0 20001123 Current and got the
> > following after installation:
> > 
> > Local package initialization:/usr/libexec/ld-elf.so.1: Shared object
> > "libc.so.4" not found
> we bumped the libc version to 5, but we didn't make compat4 libaries
> available for installation yet.

In this case it doesn't matter -- "a fresh hard drive" and "local
package" implies that the -current packages on ftp.freebsd.org haven't
been built since the bump and are thus slightly out dated.

> I'll renew my annoyance with the fact that we just bumped this without
> even figuring out why things broke or if we could change them in a way
> to save functionality without having to bump the version number[1].

It doesn't matter as at least Garrett has some changes he's going to make
that aren't compatible.  libc.so will be at least at version "5" in
FreeBSD 5.0, so we'll have to go thru this pain eventually anyway.

> We also never propagated this bump to RELENG_4, so the release shipped
> with the worst of both worlds.

Huh?  Why the worst of both worlds??
> To answer your question, though:
>       I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible
> should happen. This should work until we get our act together regarding
> this change.

I'm not quite sure what isn't together other than no compat4x libc.so.4
yet -- I can certainly create one, but I'll have to update it for the
libc.so.4 in 4.3 and 4.4.  Don't forget the compat libs are uuencoded
files, so CVS will see large diffs.  If people don't mind, I'll certainly
make the compat libs now.

          GNU is Not Unix / Linux Is Not UniX

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to