From owner-freebsd-isdn Sat Sep 26 16:26:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02667 for freebsd-isdn-outgoing; Sat, 26 Sep 1998 16:26:55 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02635 for ; Sat, 26 Sep 1998 16:26:42 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.7) with SMTP id AAA10107; Sun, 27 Sep 1998 00:26:40 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sun, 27 Sep 1998 00:26:40 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Wolfgang Helbig cc: freebsd-isdn@FreeBSD.ORG, hm@kts.org Subject: Re: i4b/YACC breakage in -STABLE? In-Reply-To: <199809261712.TAA12237@RVC1.Informatik.BA-Stuttgart.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Wolfgang Helbig wrote: > I fixed a similar problem for FreeBSD current by changing some > statements in the Makefile. These changes take effect only under the > condition ${BSDTYPE}==FREEBSD && ${RELEASE}=="3.0-CURRENT". I had spotted those, and tried editing the makefile to activate the -CURRENT behaviour. I must have got it wrong somehow, as it didn't work. > You might want to try out these changes by lying to make: > > make clean > RELEASE="3.0-CURRENT" make This did work however. > If this works, we might have to prepare for RELEASE=="2.2.8", the next > 2... release. (And for 3.0-RELEASE) Isn't there something better we can do? Like explicitly invoking yacc from the makefile rather than relying on the default rule from bsd.def.mk maybe? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message