In message: <[EMAIL PROTECTED]>
"Steven G. Kargl" <[EMAIL PROTECTED]> writes:
: M. Warner Losh said:
: > In message: <[EMAIL PROTECTED]>
: > "Steven G. Kargl" <[EMAIL PROTECTED]> writes:
: > : M. Warner Losh said:
: > : > In message: <[EMAIL PROTECTED]>
: > : > "Steven G. Kargl" <[EMAIL PROTECTED]> writes:
: > : > : Could someone add the following patch to UPDATING?
: > : > : Change the words to whatever suits your fancy.
: > : >
: > : > I'm trying to devise a good way to deal with this breakage and hope it
: > : > is transient. I'm not hopeful :-( I'll consider adding this to UPDATING.
: > : >
: > :
: > : Any user who installed DP1 and a bunch of ports will
: > : have a unpleasant experience when they update to
: > : post 20021031 sources. All their ports will stop
: > : working and it isn't a simple matter to update
: > : those ports.
: >
: > I thought DP1 didn't generate binaries or libraries that contained
: > __sF.
: >
:
: http://www.freebsd.org/releases/5.0R/schedule.html
:
: DP1 was released on 5 Apr 2002. This may have occurred during
: Peter's last attempt at killing __sF. DP2 is in progress
: according to the web page and __sF should not be present.
: There will also be that group of -current users who lag
: a few weeks behind in their buildworlds.
But std{in,out,err} #defines were changes from __sF to
__std{in,out,err}p almost a year ago. That's what causes __sF to
appear...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
