public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/24835] powerpc build breaker with Werror=odr
Date: Sat, 30 Jul 2022 01:27:47 +0000	[thread overview]
Message-ID: <bug-24835-4717-bYbGpAEaUm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24835-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24835

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |keiths at redhat dot com

--- Comment #2 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Tom Tromey from comment #1)
> Is it enough to just remove that 'const' from regdat.sh?
> That seems like an unobjectionable patch to me.

It is enough to get PowerPC building again. The question is,
would we rather change everything to 'const' instead? While
noticeably less trivial, it does work. [Tested on x86_64,
aarch64, ppc64le, s390x rawhide scratch-builds enabling LTO.]

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

  parent reply	other threads:[~2022-07-30  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24835-4717@http.sourceware.org/bugzilla/>
2022-02-27 23:07 ` tromey at sourceware dot org
2022-07-30  1:27 ` keiths at redhat dot com [this message]
2022-09-09  0:56 ` tromey at sourceware dot org
2022-09-09  0:56 ` tromey at sourceware dot org
2022-11-10 22:09 ` tromey at sourceware dot org
2022-11-11  5:31 ` sam at gentoo 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-24835-4717-bYbGpAEaUm@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).