public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31330] Glibc[2.31|2.30|2.29|2.28] build hang on Fedora 39 Date: Wed, 07 Feb 2024 22:06:55 +0000 [thread overview] Message-ID: <bug-31330-131-MTGK5lQWYc@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31330-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31330 --- Comment #4 from Carlos O'Donell <carlos at redhat dot com> --- (In reply to Mikael Pettersson from comment #3) > Possibly related: I've seen very similar issues building(*) that era glibc:s > with make-4.4. Switching to make-4.3 worked for me. This is what I would expect to be the difference really. There have been some make 4.3 to make 4.4 issues.(In reply to skpgkp1 from comment #2) > I reproduced build hang issue in 2.32 and bisected. Build hang issue on > fedora 39 fixed by following commit in glibc 2.32. > > f13d260190 signal: Move sys_errlist to a compat symbol > > I think following 3 commits are related. > > f13d260190 signal: Move sys_errlist to a compat symbol > b1ccfc061f signal: Move sys_siglist to a compat symbol > e4e11b1dba signal: Add signum-{generic,arch}.h > > Can you please look into these commit to see whether they can be bckported > to 2.31, 2.30, 2.29 and 2.28 branches. They cannot be backported. I don't think these are the actual issues. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-07 22:06 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 18:48 [Bug build/31330] New: " skpgkp1 at gmail dot com 2024-02-02 21:41 ` [Bug build/31330] " carlos at redhat dot com 2024-02-03 16:52 ` skpgkp1 at gmail dot com 2024-02-04 13:22 ` mikpelinux at gmail dot com 2024-02-07 22:06 ` carlos at redhat dot com [this message] 2024-02-07 22:10 ` sam at gentoo dot org 2024-02-07 22:25 ` adhemerval.zanella at linaro dot org 2024-02-08 0:46 ` skpgkp1 at gmail dot com 2024-02-08 12:59 ` carlos at redhat dot com 2024-05-10 3:08 ` cvs-commit at gcc dot gnu.org 2024-05-10 3:11 ` cvs-commit at gcc dot gnu.org 2024-05-10 3:14 ` cvs-commit at gcc dot gnu.org 2024-05-10 3:16 ` cvs-commit at gcc dot gnu.org 2024-05-10 3:17 ` hjl.tools at gmail dot com 2024-05-10 3:18 ` hjl.tools at gmail 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-31330-131-MTGK5lQWYc@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).