public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stli at linux dot ibm.com" <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: Mon, 08 Jan 2024 14:28:34 +0000 [thread overview] Message-ID: <bug-31196-131-PsgThQsf8I@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31196-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31196 Stefan Liebler <stli at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stli at linux dot ibm.com --- Comment #2 from Stefan Liebler <stli at linux dot ibm.com> --- I've also tried with 2.38 release branch (cfe121910013a46e2477562282c56ae8062089aa) with gcc 13 (5d0d592c486c31bd9c26af0d1f0a7b6a3d68c22b) and I don't get a build fail. If you manually run the gcc-compile-command producing strchrnul-c.os in <glibc-src>/string/ with -save-temps, the strchrnul-c.i file should have included <glibc-src>/string/strchrnul.c with __strchrnul_c instead of __strchrnul. Then the internal symbol __GI___strchrnul should be __strchrnul_c (See your error-message from <glibc-src>/sysdeps/s390/strchrnul-c.c). The weak_alias should be the IFUNC __strchrnul (See <glibc-src>/sysdeps/s390/strchrnul.c) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-08 14:28 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 [this message] 2024-01-14 23:13 ` dilfridge at gentoo dot org 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-PsgThQsf8I@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: linkBe 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).