Date: Fri, 08 Nov 2002 14:47:47 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "M. Warner Losh" <imp@bsdimp.com> 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 Message-ID: <3DCC3F13.1CB12A9E@mindspring.com> References: <20021108.092732.124899267.imp@bsdimp.com> <Pine.GSO.4.10.10211081205020.27766-100000@pcnet1.pcnet.com> <20021108174915.GA71225@troutmask.apl.washington.edu> <20021108.143019.08321200.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DCC3F13.1CB12A9E>