From: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>
To: gcc-bugs@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict in objc-parse.y
Date: Mon, 27 Jan 2003 22:18:00 -0000 [thread overview]
Message-ID: <15925.41446.453524.952565@perceval.inria.fr> (raw)
A fresh checkout of 3.2.2 branch fails to bootstrap on an i686-pc-linux.
The failure happens for Objective-C as a reduce/reduce conflict in
objc-parse.y. I can't locate a recent change to that file. So I
guess it must be something having to do my settings. I'm using Bison
1.875. Is anyone seeing this failure?
(I'm running another bootstrap on a different machine)
-- Gaby
[...]
stage1/xgcc -Bstage1/ -B/u/molotova/0/galaad/gdosreis/.target/i686-pc-linux-gnu/i686-pc-linux-gnu/bin/ -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc -I/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/. -I/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/config -I/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/../include -I/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/objc \
-c /u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/objc/objc-lang.c -o objc-lang.o
cd /u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/objc; \
if bison -o op$$.c objc-parse.y ; then \
test -f op$$.output && mv -f op$$.output objc-parse.output ; \
mv -f op$$.c objc-parse.c ; \
else \
rm -f op$$.* ; \
false ; \
fi
objc-parse.y: conflicts: 31 shift/reduce, 1 reduce/reduce
objc-parse.y: expected 0 reduce/reduce conflicts
make[2]: *** [/u/molotova/0/galaad/gdosreis/src/redhat/gcc-3.2/gcc/objc/objc-parse.c] Error 1
make[2]: Leaving directory `/0/var/tmp/gdr/gcc/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/0/var/tmp/gdr/gcc/gcc'
make: *** [bootstrap] Error 2
next reply other threads:[~2003-01-27 21:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 22:18 Gabriel Dos_Reis [this message]
2003-01-27 22:32 ` Gabriel Dos Reis
2003-01-27 22:52 ` Paolo Carlini
2003-01-27 23:10 ` Gabriel Dos Reis
2003-01-28 0:03 ` Raja R Harinath
2003-01-28 0:23 ` Gabriel Dos Reis
2003-01-27 22:56 ` Joseph S. Myers
2003-01-27 23:20 ` Gabriel Dos Reis
2003-01-28 1:47 ` Ziemowit Laski
2003-01-28 5:19 ` Gabriel Dos_Reis
2003-01-28 11:39 ` Joseph S. Myers
2003-01-28 12:43 ` Gabriel Dos Reis
2003-01-29 0:54 ` Ziemowit Laski
2003-01-29 1:32 ` Joseph S. Myers
2003-01-29 1:49 ` Ziemowit Laski
2003-01-29 2:18 ` Joseph S. Myers
2003-01-29 4:09 ` Stan Shebs
2003-01-30 2:01 ` Joe Buck
2003-01-29 6:02 ` Ziemowit Laski
2003-01-30 1:43 ` Joe Buck
2003-01-30 2:07 ` Joseph S. Myers
2003-01-30 3:40 ` Joe Buck
2003-01-30 4:20 ` Ziemowit Laski
2003-01-30 4:27 ` Joseph S. Myers
2003-01-30 6:56 ` Ziemowit Laski
2003-01-30 11:07 ` Neil Booth
2003-01-30 14:04 ` Mark Mitchell
2003-01-30 22:43 ` Neil Booth
2003-01-30 23:59 ` Ziemowit Laski
2003-01-31 13:26 ` Joseph S. Myers
2003-01-31 21:41 ` Ziemowit Laski
2003-01-28 14:04 Paolo Bonzini
2003-01-30 23:38 Paolo Bonzini
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=15925.41446.453524.952565@perceval.inria.fr \
--to=gdosreis@sophia.inria.fr \
--cc=gcc-bugs@gcc.gnu.org \
--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).