Re: s390x: removal of 31-bit libraries
Aurelien Jarno <[email protected]> Tue, 28 Apr 2026 18:47:19 +0200
| Newsgroups | gmane.linux.debian.devel.glibc,gmane.linux.debian.ports.s390,gmane.linux.debian.devel.gcc,gmane.linux.debian.devel.kernel,gmane.linux.debian.devel.release |
|---|---|
| Message-ID | <[email protected]> |
Hi,
On 2026-04-28 10:22, Sebastian Ramacher wrote:
> Hi
>
> On 2025-12-29 13:12:48 +0100, Aurelien Jarno wrote:
> > Hi,
> >
> > Linux 6.19 will drop support for 31-bit compatibility on s390x, and will
> > also stop providing 31-bit support in UAPI header files [1]. Once this
> > lands in unstable, it will become impossible to build the libc6-s390 and
> > libc6-dev-s390 packages on s390x. We should therefore stop building
> > these packages, as well as g++-15-multilib and the corresponding lib32*
> > libraries.
> >
> > Doing so will break many packages. I therefore suggest that, over the
> > next few weeks, we start removing 31-bit support in all packages except
> > src:gcc-15, src:gcc-defaults, src:glibc, src:linux and src:zlib (and
> > possibly the corresponding cross compilers?). Then in a final
> > coordinated step, we can fully drop 31-bit support from those remaining
> > packages as well.
> >
> > Any thoughts about that? Volunteers to coordinate this?
>
> If I am reading dak output correctly, we are down to gcc-11, gcc-13,
> gcc-14, gcc-15, zlib, and glibc itself. So assuming that I didn't miss
> anything, are we there to also drop the support from these packages?
These packages have already been fixed, but they are kept as cruft in
sid (but not in forky). I have not investigated why, it could just be
that dak is not smart enough.
In addition llvm-toolchain-{14,19,20} are still waiting for a fix [1],
but they are only in sid or experimental.
Regards
Aurelien
[1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=31-bit-removal;[email protected]