Date: Thu, 07 Nov 2002 10:42:51 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: jdp@polstra.com Cc: current@freebsd.org Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021107.104251.110765870.imp@bsdimp.com> In-Reply-To: <200211071640.gA7GeWJk065460@vashon.polstra.com> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <20021106.231940.123343134.imp@bsdimp.com> <200211071640.gA7GeWJk065460@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200211071640.gA7GeWJk065460@vashon.polstra.com> John Polstra <jdp@polstra.com> writes: : In article <20021106.231940.123343134.imp@bsdimp.com>, : M. Warner Losh <imp@bsdimp.com> wrote: : > In message: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> : > "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> 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. : : FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on : -current is to make __sF global again and arrange for: : : stdin == &__sF[0] : stdout == &__sF[1] : stderr == &__sF[2] Why does cvsup need this to be the case? Now you have me curious. Warner 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?20021107.104251.110765870.imp>