public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30286] Build error in split-name.h macro DOT
Date: Mon, 28 Aug 2023 14:02:09 +0000	[thread overview]
Message-ID: <bug-30286-4717-haQzPokKxk@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 #3 from Tom Tromey <tromey at sourceware dot org> ---
Bison 2.3, released in 2006, with many releases after...
maybe this is another one of those "Apple hates GPLv3" things?
I'd suggest trying to build with a bison from brew.  However
if we know that 2.3 works otherwise, I guess it is pretty
easy to rename split_style::DOT.
But -- do we know this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-28 14:02 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 [this message]
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-haQzPokKxk@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: 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).