Date: Mon, 12 Feb 2001 18:41:52 -0700 From: Warner Losh <imp@harmony.village.org> To: Alfred Perlstein <bright@wintelcom.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Message-ID: <200102130141.f1D1fqW34023@harmony.village.org> In-Reply-To: Your message of "Mon, 12 Feb 2001 17:38:58 PST." <20010212173858.Q3274@fw.wintelcom.net> References: <20010212173858.Q3274@fw.wintelcom.net> <xzpd7cno08x.fsf@flood.ping.uio.no> <200102130105.f1D15aU56009@mobile.wemm.org> <xzpd7cno08x.fsf@flood.ping.uio.no> <200102130126.f1D1Q6W33680@harmony.village.org> <20010212173410.O3038@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010212173858.Q3274@fw.wintelcom.net> Alfred Perlstein writes:
: > Actually going from libc.so.500 to libc.so.{x<500} is easy.
: > Copy libc.so.500 into /usr/lib/compat. When the libc.so link is made to
: > libc.so.{x<500}, that is the lib version number that will get burned into
: > objects. After the first `make world', rm /usr/lib/libc.so.500.
:
: If that's true it doesn't seem like it would be terribly hard to
: add a check to the installworld / world target to check for cross
: version upgrades and do the magic (or at least print out those
: instructions).
Actaully, I think that the libc.so.500 can remain in its place because
of bsd.lib.mk:
...
SHLIB_NAME= lib${LIB}.so.${SHLIB_MAJOR}
SHLIB_LINK?= lib${LIB}.so
...
.if defined(SHLIB_LINK)
@ln -sf ${SHLIB_NAME} ${SHLIB_LINK}
.endif
...
As peter pointed out, it is the libc.so link that makes it the
default.
Warner
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?200102130141.f1D1fqW34023>