From owner-freebsd-current Fri Jun 12 00:02:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18710 for freebsd-current-outgoing; Fri, 12 Jun 1998 00:02:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18702 for ; Fri, 12 Jun 1998 00:02:53 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA13579; Fri, 12 Jun 1998 17:02:50 +1000 Date: Fri, 12 Jun 1998 17:02:50 +1000 From: Bruce Evans Message-Id: <199806120702.RAA13579@godzilla.zeta.org.au> To: bde@zeta.org.au, ianh@tortuga.com.au Subject: Re: src Makefile fix Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't see how this actually works - it doesn't rename y.tab.h. This >... >I was basing the functionality on the yacc man page: > > -o output_filename > Cause yacc to write the generated code to output_filename instead > of the default file, y.tab.c. But we're fixing the case where -o can not be used :-). >Another problem is that it'll try to "mv" the generated .c even if the >"yacc" failed. As we both agree, it is not nice. The shell is execed with -e to avoid problems like that. OTOH, the mv is not nice because it is given in the same command as the yacc, so it causes an extra exec, and it turns the #line statements in y.tab.c into garbage. >Shall I sit back and patiently await a good fix, or continue the hunt? What was wrong with my fix except it hasn't been tested enough? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message