From owner-freebsd-current Fri Nov 8 15:13:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 664C337B629 for ; Fri, 8 Nov 2002 15:13:11 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D42E643E42 for ; Fri, 8 Nov 2002 15:13:10 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id gA8ND0PM011474; Fri, 8 Nov 2002 18:13:01 -0500 (EST) Date: Fri, 8 Nov 2002 18:13:00 -0500 (EST) From: Daniel Eischen To: "M. Warner Losh" Cc: ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING In-Reply-To: <20021108.142609.112624839.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Nov 2002, M. Warner Losh wrote: > In message: > Daniel Eischen 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. I don't think this is a show-stopper. Just recompile all your ports or use the pre-built 5.0 packages. > : 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. Could you put __sF in it's own file, and put the error in a .init section? We don't care about static binaries, right? They shouldn't have a problem. > This is not a fly in the pointment, but rather a major incompatibility > that makes it impossible to have a reasonable mix. If it's really a hassle for folks, then just provide the optional compatability hack and make them rebuild libc. Or provide a pre-built version that doesn't get installed by default. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message