From: Jung-uk Kim <jkim at FreeBSD.org>
To: devel@acpica.org
Subject: Re: [Devel] ACPICA version 20130927 released
Date: Tue, 01 Oct 2013 14:25:17 -0400 [thread overview]
Message-ID: <524B138D.8070702@FreeBSD.org> (raw)
In-Reply-To: 1AE640813FDE7649BE1B193DEA596E880246778F@SHSMSX101.ccr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
-----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. ;-)
> 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
Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)
iQEcBAEBAgAGBQJSSxOMAAoJEHyflib82/FGEacH+wfPhh+HNvt448L0W0tRd329
5RABk2PgK0ijWhsxEszz92bAIGqs4NXhpR44l8D4grfWaIYVWpGXjeVi0T/uz7Ca
oVu+U9yDHCBJcmftWe13Qg++oaujWZcpaSPC5vvc+mlbhcl+91ldk2cJ7ImAhN2E
PBwmikGuy+iioeZTbY+d7sZEMX55d0ZmXpR4PVT1udPwSq0PkLnRsT6GO+3vXamx
RKaq35U/aQFelyRfFA3d63pHOdA+tACsBNpuR/em/hQHYJwNTm7xY+vmy+rI5y2S
YJ6i7fh5mgfq8fUINq6Kpn12sKAhRi3L9U7Mfu0+pT1Qw3TQl0hd1qYhhsBk1UE=
=CVe9
-----END PGP SIGNATURE-----
next reply other threads:[~2013-10-01 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 18:25 Jung-uk Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-02 16:15 [Devel] ACPICA version 20130927 released Moore, Robert
2013-10-01 22:56 Moore, Robert
2013-10-01 22:42 Zheng, Lv
2013-09-30 22:54 Zheng, Lv
2013-09-30 22:50 Zheng, Lv
2013-09-30 22:28 Zheng, Lv
2013-09-30 17:40 Jung-uk Kim
2013-09-30 17:11 Jung-uk Kim
2013-09-27 16:59 Moore, Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524B138D.8070702@FreeBSD.org \
--to=devel@acpica.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.