From: Vincent Li <vincent.mc.li@gmail.com>
To: development@lists.ipfire.org
Cc: michael.tremer@ipfire.org
Subject: Potential glibc 2.44 bug for loongarch64
Date: Fri, 23 Oct 2026 02:23:19 +0000 (UTC) [thread overview]
Message-ID: <cec2f3bd-7aa7-6aa9-fd96-f37d2737d6c@gmail.com> (raw)
Hi Michael,
I mirrored your core205 toochain upgrade including glibc 2.43 to 2.44
update to the loongfire repo which is fork of ipfire on loongarch64. I
noticed I could not install the ISO on loongarch machine after glibc
update, if I only revert glibc 2.44 back to 2.43 in the toolchain, no
installation issue. I assume IPFire loongarch port would have same issue
since the loongfire fork has exact same installer code as IPFire. I filed
a bugzilla report to sourceware for glibc.
https://sourceware.org/bugzilla/show_bug.cgi?id=34861
Best,
Vincent
next reply other threads:[~2026-10-23 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 2:23 Vincent Li [this message]
2026-10-23 9:32 ` Michael Tremer
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=cec2f3bd-7aa7-6aa9-fd96-f37d2737d6c@gmail.com \
--to=vincent.mc.li@gmail.com \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.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