From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Craig Rodrigues <rodrigc@attbi.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Bison 1.75c + FreeBSD 5.0 = can't boostrap gcc from CVS
Date: Thu, 12 Dec 2002 11:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212121922220.29906-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20021211230706.A38104@attbi.com>
On Wed, 11 Dec 2002, Craig Rodrigues wrote:
> When I tried to bootstrap, I got this error:
>
> gcc -c -DIN_GCC -DLOCALEDIR=\"/home/rodrigc/testgcc/build/run/share/locale\" -DLOCALE_ALIAS_PATH=\"/home/rodrigc/testgcc/build/run/share/locale\" -DLIBDIR=\"/home/rodrigc/testgcc/build/run/lib\" -DHAVE_CONFIG_H -I.. -I. -I../../../gcc/gcc/intl -I../../../gcc/gcc -I../../../gcc/gcc/config -I../../../gcc/gcc/../include -g -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -fno-common ../../../gcc/gcc/intl/ngettext.c -o ngettext.o
> bison -y -d --name-prefix=__gettext --output plural.c ../../../gcc/gcc/intl/plural.y
> conflicts: 7 shift/reduce
> ../../../gcc/gcc/intl/plural.y: expected 10 shift/reduce conflicts
> *** Error code 1
(a) This is a known gettext problem (that the number of expected conflicts
is incorrect). We should update the intl directory to current gettext,
but not before the 3.3 branch.
(b) We need to investigate and fix why the plural.c file in CVS isn't
being used here.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2002-12-12 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 21:15 Craig Rodrigues
2002-12-12 11:52 ` Joseph S. Myers [this message]
2002-12-12 17:18 ` Loren James Rittle
2002-12-13 12:06 ` Joseph S. Myers
2002-12-27 7:45 ` Gerald Pfeifer
2002-12-29 14:15 ` PATCH contrib/gcc_update (was: Bison 1.75c + FreeBSD 5.0 = can't boostrap gcc from CVS) Gerald Pfeifer
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=Pine.LNX.4.33.0212121922220.29906-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=rodrigc@attbi.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).