From: Vincent Li <vincent.mc.li@gmail.com>
To: development@lists.ipfire.org
Cc: michael.tremer@ipfire.org
Subject: dracut-ng fix for glibc 2.44 fts regression — LoongArch build
Date: Mon, 26 Oct 2026 02:47:43 +0000 (UTC) [thread overview]
Message-ID: <c3d60ab-a8d-13b7-4231-aa4a1bee82ed@gmail.com> (raw)
Hi Michael,
Sorry, I deleted the email about the potential glibc 2.44 regression
https://sourceware.org/bugzilla/show_bug.cgi?id=34861, so I'm
starting a new thread.
From https://sourceware.org/bugzilla/show_bug.cgi?id=34078, I confirmed
that my LoongArch build environment needs the fix from
https://github.com/dracut-ng/dracut-ng/pull/2394 to work around the glibc
2.44 issue. dracut-ng 112 already includes the fix.
Do you think it's a good idea to carry the dracut-ng fix in the IPFire
build for LoongArch, even though the IPFire build environment doesn't
currently experience this issue?
Best,
Vincent
next reply other threads:[~2026-10-26 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 2:47 Vincent Li [this message]
2026-10-26 10:15 ` Adolf Belka
2026-10-26 23:38 ` Vincent Li
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=c3d60ab-a8d-13b7-4231-aa4a1bee82ed@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