From: Matthias Klose <doko@cs.tu-berlin.de>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, mark@codesourcery.com, debian-gcc@lists.debian.org
Subject: Re: [3.2] Reconsider patches for bison 1.50?
Date: Mon, 21 Oct 2002 02:16:00 -0000 [thread overview]
Message-ID: <15795.12481.863443.773302@gargle.gargle.HOWL> (raw)
In-Reply-To: <20021020214101.GA31693@codesourcery.com>
Zack Weinberg writes:
> This is a quote from the Debian package changelog for gcc 3.2:
>
> * FTBS: With the switch to bison-1.50 (and 1.75), gcc-3.2 fails to build from
> source on Debian unstable systems. This is fixed in gcc HEAD, but not on
> the current release branch.
> HELP NEEDED:
> - check what is missing from the patches in debian/patches/bison.dpatch.
> This is a backport of the bison related patches, but showing regressions
> in the gcc testsuite, so it cannot be applied.
> - build gcc using byacc (bootstrap currently fails using byacc).
> - build bison-1.35 in it's own package (the current 1.35-3 package fails
> to build form source).
> - and finally ask upstream to backport the patch to the branch. It's not
> helpful not beeing able to follow the stable branch. Maybe we should
> just switch to gcc HEAD as BSD does ...
> As a terrible workaround, build the sources from CVS first on a machine,
> with bison-1.35 installed, then package the tarball, so the bison
> generated files are not rebuilt.
>
> I think we should reconsider not backporting the patches for bison 1.50
> to the 3.2 branch.
btw, I noticed the very same regressions on HEAD hppa-linux, but not
on HEAD i386-linux.
next prev parent reply other threads:[~2002-10-20 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 0:56 Zack Weinberg
2002-10-21 2:16 ` Matthias Klose [this message]
2002-10-21 8:37 ` Mark Mitchell
2002-10-21 8:40 ` Matthias Klose
2002-10-21 11:47 ` Mark Mitchell
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=15795.12481.863443.773302@gargle.gargle.HOWL \
--to=doko@cs.tu-berlin.de \
--cc=debian-gcc@lists.debian.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=zack@codesourcery.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).