Date: Fri, 08 Nov 2002 14:26:09 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: eischen@pcnet1.pcnet.com Cc: ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021108.142609.112624839.imp@bsdimp.com> In-Reply-To: <Pine.GSO.4.10.10211081205020.27766-100000@pcnet1.pcnet.com> References: <20021108.092732.124899267.imp@bsdimp.com> <Pine.GSO.4.10.10211081205020.27766-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <Pine.GSO.4.10.10211081205020.27766-100000@pcnet1.pcnet.com>
Daniel Eischen <eischen@pcnet1.pcnet.com> writes:
: All the ports are going to be rebuilt for the release anyways,
: so this doesn't affect fresh installs, correct? It is only a
: problem when mixing older 4.x and 5.0 libraries/binaries with
: __sF-free libc (if I understand things correctly).
The problem is that you cannot have 4.x packages and 5.x packages
co-mingled on the same system. that's what I'm trying to fix. You'd
have to rebuild the 4.x packages before they are fixed.
: This is 5.0; it is a major release and there will be some flies
: in the ointment. I say bite the bullet now -- don't wait.
: If we want to provide an optional compatability hack to libc
: so that folks can compile it with __sF support, then I think
: that is better than leaving __sF in the release, perhaps
: with a mktemp(3)-like warning if possible (?).
You'd need a run-time warning for this to be effective. I'm not sure
that ld.so can do this right now.
This is not a fly in the pointment, but rather a major incompatibility
that makes it impossible to have a reasonable mix.
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?20021108.142609.112624839.imp>