public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29575] [2.35/2.36]: Many testsuite failures when not building with "--disable-default-pie" on sparc*-linux-*
Date: Mon, 07 Nov 2022 06:54:18 +0000 [thread overview]
Message-ID: <bug-29575-131-YpVfGHoaVY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29575-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29575
Sam James <sam at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sam at gentoo dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-07 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 8:44 [Bug build/29575] New: [Regression 2.34/2.25]: Large number of testsuite failures on sparc*-linux-*-* glaubitz at physik dot fu-berlin.de
2022-09-16 11:43 ` [Bug build/29575] " carlos at redhat dot com
2022-09-30 8:53 ` glaubitz at physik dot fu-berlin.de
2022-09-30 8:53 ` [Bug build/29575] [Regression 2.34/2.25]: Many testsuite failures when not building with "--disable-default-pie" on sparc*-linux-* glaubitz at physik dot fu-berlin.de
2022-09-30 8:54 ` [Bug build/29575] [2.35/2.36]: " glaubitz at physik dot fu-berlin.de
2022-10-04 17:32 ` adhemerval.zanella at linaro dot org
2022-11-06 15:08 ` glaubitz at physik dot fu-berlin.de
2022-11-07 6:54 ` sam at gentoo dot org [this message]
2022-11-12 23:44 ` glaubitz at physik dot fu-berlin.de
2023-07-19 11:48 ` glaubitz at physik dot fu-berlin.de
2023-07-19 12:46 ` adhemerval.zanella at linaro 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-29575-131-YpVfGHoaVY@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).