From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC, PATCH] YACC parsers
Date: Mon, 19 Dec 2011 15:15:00 -0000 [thread overview]
Message-ID: <m3aa6owqey.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201112171937.pBHJbDhq010089@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Sat, 17 Dec 2011 20:37:14 +0100 (CET)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> It may not be impossible to "fix" the OpenBSD yacc(4) here, but given
Mark> the fact that it supports the -p option to add a prefix to all the
Mark> relevant symbols that would be somewhat silly. Unfortunately,
Mark> changing the build infrastructure to use yacc -p isn't exactly
Mark> trivial.
Mark> Opinions?
What is hard about using yacc -p?
I wouldn't mind getting rid of these hacks and requiring a -p-capable
yacc. Or even requiring Bison; I think this would only be needed by gdb
developers anyhow.
Tom
next prev parent reply other threads:[~2011-12-19 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 19:40 Mark Kettenis
2011-12-18 6:21 ` Joel Brobecker
2011-12-19 15:15 ` Tom Tromey [this message]
2011-12-19 15:39 ` Mark Kettenis
2011-12-19 16:13 ` Tom Tromey
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=m3aa6owqey.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox