Date: Mon, 12 Feb 2001 17:51:08 -0800 From: "David O'Brien" <TrimYourCc@NUXI.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Message-ID: <20010212175108.R3038@dragon.nuxi.com> In-Reply-To: <xzplmrbmk94.fsf@flood.ping.uio.no>; from des@ofug.org on Tue, Feb 13, 2001 at 02:42:15AM %2B0100 References: <200102130120.f1D1KpU56194@mobile.wemm.org> <200102130131.f1D1VrW33790@harmony.village.org> <xzplmrbmk94.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 13, 2001 at 02:42:15AM +0100, Dag-Erling Smorgrav wrote:
> Warner Losh <imp@harmony.village.org> writes:
> > I've had problems in the past going backwards on major versions of
> > shared libaries. The major problem is that if I have binaries that
> > refer to libc.so.503, then when the major number is reverted back to
> > 5, it is a nop because ld will use libc.so.503 for new binaries.
>
> When we back down to 5, we add magic to the Makefiles to move
> libc.so.5?? to /usr/lib/compat - that way they're only used when
> needed at runtime, not for linking new programs.
NO! No magic. No polution. If you are using -current when libc.so.5003
exists, you should be able to handle the `mv' yourself manually.
--
-- David (obrien@FreeBSD.org)
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010212175108.R3038>