From: Kelley Cook <kcook@gcc.gnu.org>
To: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>,
gdb@sources.redhat.com, drow@false.org,
DJ Delorie <dj@redhat.com>,
binutils@sources.redhat.com
Subject: Re: bison problem
Date: Fri, 24 Sep 2004 18:48:00 -0000 [thread overview]
Message-ID: <20040924184801.10426.qmail@web41521.mail.yahoo.com> (raw)
In-Reply-To: <200409241808.i8OI8iu3029162@tully.CS.Berkeley.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 900 bytes --]
--- Paul Hilfinger <hilfingr@EECS.Berkeley.EDU> wrote:
>
> Daniel & Kelley,
>
> Oh dear. I went and changed the GDB Makefile.in, assuming that was
> intended, so that it conforms to Kelley's patch. Sorry. My bad.
>
> Paul Hilfinger
A grep search shows that GCC has no need for either the old or new
ylwrap. So which version is chosen for src/ is immaterial to me.
If anyone wishes to make sure that everything within src/ works with
the new-style ylwrap ("new-style" apparently being 1998, when ylwrap's
command order changed) and re-upgrade the toplevel in both trees then
please feel free. Though it may be a nice cleanup, as I don't even
have write access to src/, I clearly won't be the one doing it.
BTW, DJ to prevent this from happening again, would it be possible to
just delete ylwrap from GCC's—but not from src's—toplevel directory as
it is not used anywhere within GCC.
KC
next prev parent reply other threads:[~2004-09-24 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 3:53 John David Anglin
2004-09-24 3:56 ` Daniel Jacobowitz
2004-09-24 18:08 ` Paul Hilfinger
2004-09-24 18:48 ` Kelley Cook [this message]
2004-09-24 20:07 ` DJ Delorie
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=20040924184801.10426.qmail@web41521.mail.yahoo.com \
--to=kcook@gcc.gnu.org \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=hilfingr@EECS.Berkeley.EDU \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).