public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8235: Problem compiling gengtype-yacc.y with bison
Date: Thu, 31 Oct 2002 15:16:00 -0000	[thread overview]
Message-ID: <20021031231602.32584.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8235; it has been noted by GNATS.

From: Joe Buck <jbuck@synopsys.com>
To: mdupont777@yahoo.com (James Michael DuPont)
Cc: Joe.Buck@synopsys.COM (Joe Buck), gcc-gnats@gcc.gnu.org,
   gcc-bugs@gcc.gnu.org
Subject: Re: c/8235: Problem compiling gengtype-yacc.y with bison
Date: Thu, 31 Oct 2002 15:09:23 -0800 (PST)

 > It is very simple,
 > the problem is that the newest version of bison chokes on the gcc
 > gengtype-yacc.y code. This silly bug tracker... 
 > 
 > Are you sure i did not send you anything usfull?
 
 I've been testing the branch, and it has no file by that name, evidently
 you are referring to the gcc code on the trunk.
 
 Could you please send a group reply to this message, saying:
 
 1) exactly which gcc version you tested;
 2) what bison version;
 3) the error output
 


             reply	other threads:[~2002-10-31 23:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 15:16 Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 22:14 neroden
2002-10-31 23:46 James Michael DuPont
2002-10-31 16:56 Pop Sébastian
2002-10-31 15:10 jbuck
2002-10-31 15:06 James Michael DuPont
2002-10-31 15:06 Joe Buck
2002-10-31 14:46 Joe Buck
2002-10-31 14:39 jbuck
2002-10-15 14:26 mdupont777

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=20021031231602.32584.qmail@sources.redhat.com \
    --to=jbuck@synopsys.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).