su 23.3.2025 klo 16.54 Samuel Thibault (sthiba...@debian.org) kirjoitti: > > Martin-Éric Racine, le dim. 23 mars 2025 13:54:11 +0200, a ecrit: > > su 23.3.2025 klo 10.06 Samuel Thibault (sthiba...@debian.org) kirjoitti: > > > Martin-Éric Racine, le dim. 23 mars 2025 09:21:49 +0200, a ecrit: > > > > X-Debbugs-Cc: debian-am...@lists.debian.org, > > > > debian-h...@lists.debian.org , martin-eric.rac...@iki.fi > > > > User: debian-am...@lists.debian.org > > > > User: debian-h...@lists.debian.org > > > > Usertags: amd64 > > > > > > > > Could gcc-multilib & dependencies be compiled for hurd-amd64 as well? > > > > Without it we're missing the -m32 flag. > > > > > > Put another way: why do you need -m32? We didn't feel it was worth > > > spending the time to fix the 32bit multilib support when that will be > > > moot in 2038 anyway. > > > > I have a package whose autoconf checks for -m32 to produce 32-bit > > binaries on 64-bit ports. Implementing this on amd64 and x32 merely > > required adding gcc-multilib to Build-Depends. hurd-64 fails that > > check because there's no gcc-multilib. > > But there are other ports that don't have a 32bit variant (e.g. > loong64), so that case exists anyway.
True, but the package in question very much is x86 anyhow i.e. 32-bit binaries should be possible on all x86 variants. Right now, hurd-amd64 is the only one not setup for this. Martin-Éric
