public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/28456] Compilation error in gdb/c-exp.y Date: Wed, 20 Oct 2021 17:18:37 +0000 [thread overview] Message-ID: <bug-28456-4717-QWGupDJdlM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28456-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28456 Christian Biesinger <cbiesinger at google dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Christian Biesinger <cbiesinger at google dot com> --- This has been pushed by simark. commit 6d81986879bbb05407e17e4788c52195897011c0 Author: Christian Biesinger <cbiesinger@google.com> AuthorDate: Fri Oct 8 16:09:46 2021 Commit: Simon Marchi <simon.marchi@efficios.com> CommitDate: Wed Oct 20 11:11:54 2021 Make c-exp.y work with Bison 3.8+ When using Bison 3.8, we get this error: ../../gdb/c-exp.y:3455:1: error: 'void c_print_token(FILE*, int, YYSTYPE)' defined but not used [-Werror=unused-function] That's because bison 3.8 removed YYPRINT support: https://savannah.gnu.org/forum/forum.php?forum_id=10047 Accordingly, this patch only defines that function for Bison < 3.8. Change-Id: I3cbf2f317630bb72810b00f2d9b2c4b99fa812ad -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-20 17:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 12:33 [Bug build/28456] New: " patrick at monnerat dot net 2021-10-15 14:57 ` [Bug build/28456] " cbiesinger at google dot com 2021-10-15 22:19 ` patrick at monnerat dot net 2021-10-20 17:18 ` cbiesinger at google dot com [this message] 2021-10-22 14:22 ` patrick at monnerat dot net
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-28456-4717-QWGupDJdlM@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).