public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/30286] Build error in split-name.h macro DOT Date: Fri, 15 Sep 2023 13:47:06 +0000 [thread overview] Message-ID: <bug-30286-4717-vGpVsKEAQn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30286-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30286 --- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fe26aa95336c0ddec01b407b990caf2c758fd93f commit fe26aa95336c0ddec01b407b990caf2c758fd93f Author: Tom Tromey <tromey@adacore.com> Date: Thu Aug 31 07:33:34 2023 -0600 Rename split_style::DOT This renames split_style::DOT, to avoid name clashes when building gdb with an old version of Bison (2.3, the version available on macOS). In particular the error looks like: ./split-name.h:34:3: error: expected identifier DOT, ^ m2-exp.c:163:13: note: expanded from macro 'DOT' Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30286 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-15 13:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-29 14:15 [Bug gdb/30286] New: " lu.xinyu0121 at foxmail dot com 2023-03-29 14:15 ` [Bug gdb/30286] " lu.xinyu0121 at foxmail dot com 2023-03-30 14:12 ` simon.marchi at polymtl dot ca 2023-03-31 14:23 ` [Bug build/30286] " tromey at sourceware dot org 2023-08-28 5:10 ` vries at gcc dot gnu.org 2023-08-28 14:02 ` tromey at sourceware dot org 2023-09-12 15:47 ` tromey at sourceware dot org 2023-09-15 13:41 ` tromey at sourceware dot org 2023-09-15 13:47 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-15 13:51 ` tromey at sourceware dot org
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-30286-4717-vGpVsKEAQn@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).