From owner-freebsd-current Fri Nov 8 14:49:30 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 6DF3E37B401 for ; Fri, 8 Nov 2002 14:49:29 -0800 (PST) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0367B43E42 for ; Fri, 8 Nov 2002 14:49:29 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0224.cvx22-bradley.dialup.earthlink.net ([209.179.198.224] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18AHwA-00009X-00; Fri, 08 Nov 2002 14:49:15 -0800 Message-ID: <3DCC3F13.1CB12A9E@mindspring.com> Date: Fri, 08 Nov 2002 14:47:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "M. Warner Losh" Cc: sgk@troutmask.apl.washington.edu, eischen@pcnet1.pcnet.com, ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING References: <20021108.092732.124899267.imp@bsdimp.com> <20021108174915.GA71225@troutmask.apl.washington.edu> <20021108.143019.08321200.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 "M. Warner Losh" wrote: > My plan is as follows: > > 1) Restore __sF to libc for 5.0. > 2) Fix 4.x binaries so that __sF isn't referened in new > binaries. This should have been done in Aug 2001, but > wasn't. > > Depending on how things go, __sF will be removed in 5.1 or 5.2 after > we have the transition period we had originally planned for 4.x, but > implemented a year ago. Before anyone's head explodes, this will *NOT* generate *new* references to __sF. Warner is *NOT* talking about changing the definitions in stdio back to their old values. *NEW* code will get the *NEW* definitions, with certain specific exceptions. The exceptions are for new code linked against old libraries, or compiled with old tools, and linked agoinst those old tools' libraries (e.g. Modula 3 and FORTRAN 95). The issue this raises is that if/when the size of struct file changes, the old programs will quit working, unless *ALL* of the libraries which reference the obsoleted symbols varsions are bumped between 4.x and 5.x, and *ALL* of them are made available as part of the binary compatability package. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message