From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: doko@cs.tu-berlin.de
Cc: begcs.debian-gcc@lists.debian.org.mark, gcc@gcc.gnu.org
Subject: Re: gcc-3_2-branch bootstrap failure when using bison-1.50
Date: Sun, 13 Oct 2002 05:03:00 -0000 [thread overview]
Message-ID: <200210130305.XAA13258@caip.rutgers.edu> (raw)
> From: Matthias Klose <doko at cs dot tu-berlin dot de>
>
> Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
> back to bison-1.35 works. HEAD does work well using bison-1.50
>
> cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
> if bison -o c-p$$.c c-parse.y; then \
> test -f c-p$$.output && mv -f c-p$$.output c-parse.output ; \
> mv -f c-p$$.c c-parse.c ; \
> else \
> rm -f c-p$$.* ; \
> false ; \
> fi
> c-parse.y:1432.2-1436.10: type clash (`' `ttype') on default action
I checked into this one, patches were submitted for the trunk and
installed back in June for these problems. E.g. see:
http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01614.html
I guess this and other similar patches for the other .y files weren't
backported to the 3.2 branch. This shouldn't be too bad since the
actual GCC-3.2.x release tar file will contain the necessary bison
output of a suitable bison version. In the mean time, I suggest just
not using bison-1.50 for testing 3.2.x CVS snapshots.
I'll leave it to our release manager to decide if this issue warrants
backporting the relevant patches or not.
Thanks for reporting this,
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next reply other threads:[~2002-10-13 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 5:03 Kaveh R. Ghazi [this message]
2002-10-13 21:37 ` Matthias Klose
2002-10-14 6:46 ` Akim Demaille
2002-10-14 7:17 ` Akim Demaille
2002-10-15 3:06 ` Matthias Klose
-- strict thread matches above, loose matches on Subject: below --
2002-10-13 5:12 Kaveh R. Ghazi
2002-10-15 1:34 ` Mark Mitchell
2002-10-15 2:18 ` Zack Weinberg
2002-10-12 18:18 Matthias Klose
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=200210130305.XAA13258@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=begcs.debian-gcc@lists.debian.org.mark \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@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).