Date: Thu, 15 Jun 2000 14:58:15 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mikko@dynas.se> To: Jan Grant <Jan.Grant@bristol.ac.uk> Cc: Mark Ovens <mark@dogma.freebsd-uk.eu.org>, pirat@access.inet.co.th, freebsd-questions@freebsd.org Subject: Re: build wine fail Message-ID: <Pine.BSF.4.21.0006151453030.317-100000@mikko.rsa.com> In-Reply-To: <Pine.GHP.4.21.0006152239090.25322-100000@mail.ilrt.bris.ac.uk>
index | next in thread | previous in thread | raw e-mail
On Thu, 15 Jun 2000, Jan Grant wrote:
> Just a thought here:
>
> People seem to be getting different results using the same sources for
> wine.
>
> The problem occurs in a .y file.
>
> What yacc-a-like are folks using? Bison? Byacc? Are their behaviours
> different for the construct:
> { unsemicoloned-C-statement }
> ?
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.)
Anyway, "make YACC='bison -y'" seems to do the trick. As would a
similar definition in /etc/make.conf.
But the real fix is of course to order and install Wine spare part
no. X67-98F87879 (A semicolon).
/Mikko
Mikko Työläjärvi_______________________________________mikko@rsasecurity.com
RSA Security
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0006151453030.317-100000>