"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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
