From owner-freebsd-current Tue Nov 23 20:56:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C157D1538F; Tue, 23 Nov 1999 20:56:24 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA25704; Tue, 23 Nov 1999 22:54:33 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 23 Nov 1999 22:54:33 -0600 (CST) From: David Scheidt To: "David O'Brien" Cc: peter.jeremy@alcatel.com.au, current@FreeBSD.ORG Subject: Re: buildworld across signal changes not quite right In-Reply-To: <19991123192454.C51014@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, David O'Brien wrote: > > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current > > buildworld running on an older -current system now progresses much > > further - in fact it now completes :-). > > Actually, I've been seeing just the opposite. > Before you could build a -CURRENT kernel and then the world. Now those > with worlds from this past summer can't build today's world regardless > of which of userland or kernel is built first. The upgrade from -STABLE is also broken because of this. The %expect stuff is blowing up. I haven't yet tried to see if building yacc and bison manually fixes things or not. I will tomorrow, when I have access to the box, assuming my workload doesn't try to kill me first. (I hadn't reported it, because I haven't had time to investigate properly. ) David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message