From owner-freebsd-current Mon Sep 24 6:57:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 4876B37B416; Mon, 24 Sep 2001 06:57:40 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id f8ODvcr92238; Mon, 24 Sep 2001 06:57:38 -0700 (PDT) (envelope-from sgk) Date: Mon, 24 Sep 2001 06:57:38 -0700 From: Steve Kargl To: Ruslan Ermilov , Peter Wemm , Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: stdin/out/err changes kill world Message-ID: <20010924065738.A92184@troutmask.apl.washington.edu> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010924132637.A63110@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Sep 24, 2001 at 01:26:37PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 24, 2001 at 01:26:37PM +1000, Peter Jeremy wrote: > On 2001-Sep-21 10:45:42 +0300, Ruslan Ermilov 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