public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kcook at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12744] [3.4 Regression] A GCC release tarball can no longer be built without bison/flex
Date: Thu, 15 Jan 2004 15:06:00 -0000 [thread overview]
Message-ID: <20040115150556.32672.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031023142355.12744.kcook@gcc.gnu.org>
------- Additional Comments From kcook at gcc dot gnu dot org 2004-01-15 15:05 -------
The above checked-in patch should fix the flex & bison tarball problem.
A missing makeinfo is still remains a problem, but that is Bug 12730 and should
be fixed soon.
If a distributor could verify that a tarball (generated with
--enable-generated-files-in-srcdir) will build without flex/bison then I propose
to close this bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12744
next prev parent reply other threads:[~2004-01-15 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 14:24 [Bug bootstrap/12744] New: " kcook at gcc dot gnu dot org
2003-10-23 14:27 ` [Bug bootstrap/12744] " kcook at gcc dot gnu dot org
2003-10-23 19:32 ` kcook at gcc dot gnu dot org
2003-10-26 19:53 ` pinskia at gcc dot gnu dot org
2003-11-04 20:59 ` kcook at gcc dot gnu dot org
2004-01-01 22:27 ` [Bug bootstrap/12744] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-10 23:30 ` steven at gcc dot gnu dot org
2004-01-15 4:02 ` cvs-commit at gcc dot gnu dot org
2004-01-15 15:06 ` kcook at gcc dot gnu dot org [this message]
2004-01-19 23:16 ` [Bug bootstrap/12744] [3.4/3.5 " kcook at gcc dot gnu dot org
2004-01-27 13:12 ` cvs-commit at gcc dot gnu dot org
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=20040115150556.32672.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).