Date: Mon, 24 Sep 2001 06:57:38 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Ruslan Ermilov <ru@FreeBSD.ORG>, Peter Wemm <peter@wemm.org>, Warner Losh <imp@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: stdin/out/err changes kill world Message-ID: <20010924065738.A92184@troutmask.apl.washington.edu> In-Reply-To: <20010924132637.A63110@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Sep 24, 2001 at 01:26:37PM %2B1000 References: <20010920123124.A6236@troutmask.apl.washington.edu> <20010921051423.3FB6438FF@overcee.netplex.com.au> <20010921102207.H27714@sunbay.com> <20010921104542.I27714@sunbay.com> <20010924132637.A63110@gsmx07.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 24, 2001 at 01:26:37PM +1000, Peter Jeremy wrote:
> On 2001-Sep-21 10:45:42 +0300, Ruslan Ermilov <ru@FreeBSD.ORG> wrote:
> >Also, this error may only be caused if:
> >
> >1. The previous ``buildworld'' installed new headers in
> > ${WORLDTMP}/usr/include.
> >
> >2. The next ``buildworld'' was run with -DNOCLEAN.
> > (Only in this case ${WORLDTMP}/usr/include will be
> > non-empty.)
>
> I have an old -CURRENT system[1] that can't do a buildworld any more,
> even with the latest bsd.{prog,lib}.mk changes (1.101 and 1.98). I
> delete /usr/obj before the buildworld, which writes off the above
> scenarios. Is anyone else seeing problems?
>
> [1] From January. I know it's old but I don't seem to have found the
> time to update lately (and I didn't realise it has been that long).
>
Yes. However, a method to get around this problem is
in src/UPDATING. I haven't tried to do the src/UPDATING
fix, yet.
--
Steve
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?20010924065738.A92184>