From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gdb@sources.redhat.com
Subject: bison problem
Date: Fri, 24 Sep 2004 03:53:00 -0000 [thread overview]
Message-ID: <200409240353.i8O3rHKB026325@hiauly1.hia.nrc.ca> (raw)
I'm assuming the following change is the cause of the build breakage
that I see today with the cvs head on hppa-unknown-linux-gnu:
2004-09-23 Kelley Cook <kcook@gcc.gnu.org>
* config.guess: New upstream version
* compile, depcomp, install-sh, ylwrap: Likewise.
...
/bin/sh ../../src/gdb/../ylwrap "bison -y" ../../src/gdb/c-exp.y y.tab.c c-exp.c
.tmp --
../../src/gdb/../ylwrap: line 109: /home/dave/gdb-6.1/objdir/gdb/bison -y: No su
ch file or directory
make[1]: *** [c-exp.c] Error 1
make[1]: Leaving directory `/home/dave/gdb-6.1/objdir/gdb'
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next reply other threads:[~2004-09-24 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 3:53 John David Anglin [this message]
2004-09-24 3:56 ` Daniel Jacobowitz
2004-09-24 18:08 ` Paul Hilfinger
2004-09-24 18:48 ` Kelley Cook
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=200409240353.i8O3rHKB026325@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gdb@sources.redhat.com \
/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).