Potential glibc 2.44 bug for loongarch64

Potential glibc 2.44 bug for loongarch64

[Vincent Li]

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

Re: Potential glibc 2.44 bug for loongarch64

[Michael Tremer]

Hello Vincent,

I am not sure we are looking at a glibc issue here - not in the sense of something being miscompiled.

I have successfully installed the ISO from here in a virtual machine using UTM:

  https://nightly.ipfire.org/next/latest/loongarch64/

It was definitely able to detect the disk and complete the installation. What branch are you building against? Can you confirm that the system has successfully detected all disks?

-Michael

> On 23 Oct 2026, at 03:23, Vincent Li <vincent.mc.li@gmail.com> wrote:
> 
> 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