public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/28302] [11 Regression] gdb fails to build with glibc 2.34 (
Date: Fri, 03 Sep 2021 13:05:46 +0000	[thread overview]
Message-ID: <bug-28302-4717-AChaETXCbe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28302-4717@http.sourceware.org/bugzilla/>

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

Luis Machado <luis.machado at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luis.machado at linaro dot org

--- Comment #1 from Luis Machado <luis.machado at linaro dot org> ---
This might have something to do with glibc's commit
6c57d320484988e87e446e2e60ce42816bf51d53, or it may have to use a new reference
for the constant.

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

  parent reply	other threads:[~2021-09-03 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  7:18 [Bug sim/28302] New: " doko at debian dot org
2021-09-03  7:18 ` [Bug sim/28302] " doko at debian dot org
2021-09-03 13:05 ` luis.machado at linaro dot org [this message]
2021-09-03 13:06 ` luis.machado at linaro dot org
2021-09-03 13:13 ` luis.machado at linaro dot org
2021-09-03 13:18 ` fweimer at redhat dot com
2021-09-09 21:59 ` [Bug sim/28302] New: " Stafford Horne
2021-09-09 22:00 ` [Bug sim/28302] " shorne at gmail dot com
2021-09-14 15:15 ` ats-sourceware at offog dot org
2021-10-03 16:09 ` vapier at gentoo dot org
2022-01-12  5:04 ` brobecker at gnat dot com
2022-01-16 10:08 ` brobecker at gnat dot com

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-28302-4717-AChaETXCbe@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).