From owner-freebsd-questions Thu Jun 15 23:22:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from access.inet.co.th (access.inet.co.th [203.151.127.252]) by hub.freebsd.org (Postfix) with ESMTP id B5BA837BD00 for ; Thu, 15 Jun 2000 23:22:43 -0700 (PDT) (envelope-from pirat@access.inet.co.th) Received: from TruPPP3526.inet.co.th (TruPPP3526.inet.co.th [203.151.127.186]) by access.inet.co.th (8.8.8/8.8.8) with ESMTP id NAA13639; Fri, 16 Jun 2000 13:21:00 +0700 (ICT) (envelope-from pirat@access.inet.co.th) Date: Fri, 16 Jun 2000 13:22:31 +0700 (ICT) From: pirat X-Sender: pirat@parwati.oaep.go.th To: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= Cc: Jan Grant , Mark Ovens , freebsd-questions@freebsd.org Subject: Re: build wine fail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Jun 2000, Mikko Ty=F6l=E4j=E4rvi wrote: > On Thu, 15 Jun 2000, Jan Grant wrote: >=20 > > Just a thought here: > >=20 > > People seem to be getting different results using the same sources for > > wine. > >=20 > > The problem occurs in a .y file. > >=20 > > What yacc-a-like are folks using? Bison? Byacc? Are their behaviours > > different for the construct: > > =09{ unsemicoloned-C-statement } > > ? >=20 > I had sort-of arrived at a similar conclusion, although I was looking > for changes made to /usr/share/mk/* (As I was under the assumption > that this particular wine version had buildable on a stock FreeBSD, > and that some change to FreeBSD has made it fail.) > >=20 > Anyway, "make YACC=3D'bison -y'" seems to do the trick. As would a > similar definition in /etc/make.conf. > what's this ? it works, "make YACC=3D'bison -y'" =20 many thanks indeed with best regards, psr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message