Yes, I think the idea was to support Bison in "yacc compatibility" mode so that
actual yacc could be used instead.
From: Zheng, Lv
Sent: Tuesday, October 01, 2013 3:42 PM
To: Jung-uk Kim; Moore, Robert; devel(a)acpica.org
Subject: RE: [Devel] ACPICA version 20130927 released
> From: Jung-uk Kim [mailto:jkim@FreeBSD.org]
> Sent: Wednesday, October 02, 2013 2:25 AM
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 2013-09-30 18:50:21 -0400, Lv Zheng wrote:
> > Hi, Kim
> > I took a look at the Makefile you are using. It seems the problem is
> > that the "--defines" is not supported by the traditional yacc. I can
> > see you are using .ORDER and empty touch to solve issues that can be
> > solved by --defines.
> > So my question is: 1. Shall we still support traditional yacc?
> We tried hard not to break POSIX Yacc support for maximum
> compatibility. In fact, I believe all *.y files were written for
> POSIX Yacc and '-y' option was used for Bison to emulate POSIX Yacc.
> GNU did not take over the world yet. ;-)
Let Bob determine this.
> > 2. Are there any better way other than using the ugly empty "touch"?
> I don't know if there's any easy way, unfortunately.
> BTW, "-o/dev/null --defines=..." looks more hackish to my eyes but it
> may be just me. :-p
:-) If POSIX yacc is going to be supported, I'll try again based on your
Thanks for the report.
> Jung-uk Kim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (FreeBSD)
> -----END PGP SIGNATURE-----