public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lu.xinyu0121 at foxmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30286] New: Build error in split-name.h macro DOT Date: Wed, 29 Mar 2023 14:15:28 +0000 [thread overview] Message-ID: <bug-30286-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30286 Bug ID: 30286 Summary: Build error in split-name.h macro DOT Product: gdb Version: 3.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: lu.xinyu0121 at foxmail dot com Target Milestone: --- When I build gdb in Mac OS 13.2.1 (22D68), it report error here. The macro DOT is conflate with enum split_style::DOT. Maybe we should replace one of the ./split-name.h:34:3: error: expected identifier DOT, ^ m2-exp.c:163:13: note: expanded from macro 'DOT' #define DOT 302 ^ In file included from m2-exp.y:42: In file included from ./language.h:26: ./symtab.h:308:23: error: expected unqualified-id style = split_style::DOT; ^ m2-exp.c:163:13: note: expanded from macro 'DOT' #define DOT 302 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-29 14:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-29 14:15 lu.xinyu0121 at foxmail dot com [this message] 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 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@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).