Re: Missing symbols file in libc6 for loong64

Hi,

> 2026=E5=B9=B45=E6=9C=8828=E6=97=A5 15:29=EF=BC=8CJohn Paul Adrian =
Glaubitz <[email protected]> =E5=86=99=E9=81=93=EF=BC=9A
>=20
> Hi Miao,
>=20
> On Thu, 2026-05-28 at 15:09 +0800, Miao Wang wrote:
>> I noticed that many binary packages on loong64 have a dependency to =
libc6 with
>> a version constraint no lower than the latest version of glibc, which =
is
>> different from other architectures, where the version constraint is =
derived
>> from the actual symbol version sused in the executables. I believe =
that it is
>> because of missing symbols file in libc6 for loong64.
>=20
> Good catch!
>=20
>> I have opened a merge request to glibc packaging adding the missing =
symbols
>> file and the merge request has been merged and is pending for upload. =
I wonder
>> what should be done to existing packages which requires a unnecessary =
higher
>> version of libc6.
>=20
> That will warrant a rebuild of the affected packages.
>=20
> Let's ask Aurelien what he thinks!

grep-dctrl -F Depends --pattern=3D"libc6 (>=3D 2.4" -s "Package,Source" =
Packages | \
tbl-dctrl -d ","  | \
sed -r 's/^([^,]*),$/\1,\1/' | \
cut -d ',' -f 2 | sort | uniq | wc -l

gives 13997

It seems that 75% the source packages should be rebuilt.

Cheers,

Miao Wang