public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilfridge at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/31196] glibc-2.38 (tip of release branch) fails to build on s390 (gcc-13 to blame?)
Date: Sun, 14 Jan 2024 23:13:39 +0000	[thread overview]
Message-ID: <bug-31196-131-y9YKxEN9pB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31196-131@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Andreas K. Huettel <dilfridge at gentoo dot org> ---
Sorry I am juggling a bit too many balls at the same time right now.

Since it's gentoo specific (apparently) it's not so urgent. => later
Not forgetting about this though (it makes our s390 stages fail).

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

  parent reply	other threads:[~2024-01-14 23:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 18:34 [Bug build/31196] New: " dilfridge at gentoo dot org
2023-12-28 18:34 ` [Bug build/31196] " dilfridge at gentoo dot org
2023-12-28 18:35 ` dilfridge at gentoo dot org
2023-12-29 13:11 ` adhemerval.zanella at linaro dot org
2024-01-08 14:28 ` stli at linux dot ibm.com
2024-01-14 23:13 ` dilfridge at gentoo dot org [this message]
2024-01-27 21:41 ` sam at gentoo dot org
2024-01-29  1:36 ` dilfridge at gentoo dot org
2024-01-29  1:37 ` [Bug build/31196] master fails to build on s390 with --disable-multi-arch dilfridge at gentoo dot org
2024-01-29 12:54 ` adhemerval.zanella at linaro dot org
2024-01-29 13:31 ` stli at linux dot ibm.com
2024-01-29 21:16 ` jsm28 at gcc dot gnu.org
2024-01-30  8:46 ` sam at gentoo dot org
2024-01-31 12:12 ` stli at linux dot ibm.com
2024-01-31 12:33 ` dilfridge at gentoo dot org
2024-02-01  9:14 ` stli at linux dot ibm.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-31196-131-y9YKxEN9pB@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).