public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92008] Build failure on cygwin
Date: Thu, 16 Apr 2020 10:14:45 +0000	[thread overview]
Message-ID: <bug-92008-4-YkFyzcRluT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92008-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92008

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
bison 1.35 doesn't, and that is what has been used last time.
Is even %define api.pure full (vs. %pure_parser) supported in much older bison
versions?  Maybe 1.875 is the oldest people do use in real-world, not sure.
Requiring bison 3 or later only is unacceptable right now.

  parent reply	other threads:[~2020-04-16 10:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92008-4@http.gcc.gnu.org/bugzilla/>
2020-04-15  4:24 ` [Bug target/92008] " pinskia at gcc dot gnu.org
2020-04-15  4:26 ` [Bug bootstrap/92008] " pinskia at gcc dot gnu.org
2020-04-15  4:53 ` pinskia at gcc dot gnu.org
2020-04-15  4:54 ` euloanty at live dot com
2020-04-15  4:57 ` pinskia at gcc dot gnu.org
2020-04-15  9:18 ` jakub at gcc dot gnu.org
2020-04-15  9:54 ` rguenth at gcc dot gnu.org
2020-04-15 11:33 ` jakub at gcc dot gnu.org
2020-04-15 16:03 ` akim.demaille at gmail dot com
2020-04-16  8:13 ` cvs-commit at gcc dot gnu.org
2020-04-16  9:55 ` cvs-commit at gcc dot gnu.org
2020-04-16  9:59 ` akim.demaille at gmail dot com
2020-04-16 10:14 ` jakub at gcc dot gnu.org [this message]
2020-04-16 10:19 ` akim.demaille at gmail dot com
2020-04-16 10:21 ` akim.demaille at gmail dot com
2020-04-16 10:44 ` jakub at gcc dot gnu.org
2020-04-16 10:46 ` jakub at gcc dot gnu.org
2020-04-16 21:27 ` wilson at gcc dot gnu.org
2020-04-21  6:24 ` akim.demaille at gmail dot com

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=bug-92008-4-YkFyzcRluT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).