From owner-freebsd-current Fri Nov 8 19:49:32 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 A08CA37B401 for ; Fri, 8 Nov 2002 19:49:30 -0800 (PST) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 451DF43E77 for ; Fri, 8 Nov 2002 19:49:26 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id gA93nKGj203786; Fri, 8 Nov 2002 22:49:21 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 8 Nov 2002 22:49:20 -0500 To: Daniel Eischen , "M. Warner Losh" From: Garance A Drosihn Subject: Re: [PATCH] note the __sF change in src/UPDATING Cc: ataraxia@cox.net, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 6:13 PM -0500 11/8/02, Daniel Eischen wrote: >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 assumes that you have the source code to everything you are running, which may not be true. This also assumes that "all you need to do" is type another 'make' in some directory, and your source code will pleasantly compile without any new problems from any of the long list of changes to include-files, ports, or the new version of gcc. Yes, every user can eventually plow their way through all that work, and by the time they do we'll probably already have 5.1-release out. Philosophically I would prefer that __sF was completely gone for 5.0-release, but at the moment I think Warner is right in saying that we need to keep it in libc until at least 5.1. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message