On Mon, Feb 17, 2025 at 8:31 PM Lucas Nussbaum <lu...@debian.org> wrote: > > Source: halide > Version: 19.0.0-5 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-2025-02-15 ftbfs-trixie > > Hi, Hi.
> During a rebuild of all packages in sid, this package failed to build > on i386. > > This package currently has binary packages on i386, so this is a regression. > > Relevant part (hopefully): > <...> > > > The full build log is available from: > http://qa-logs.debian.net/2025-02-15/halide_19.0.0-5_unstable-i386.log It says: DC-System-Info: 8 cores (Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz), 32516492 kB RAM ... which is ~32GB of RAM. Are many packages being rebuilt at the same time on the same machine, or only one at the time? I'm a bit unsure why it built on buildd successfully, but is failing now. I see several options: 1. This //seems// like buildd issue, because i don't recall seeing it when building for i386 package using i386 chroot. Can it be somehow told not to build other packages at the same time? 2. Wait for LLVM20, maybe memory consumption has improved there. 3. Adjust the package to allow cross-compilation from amd64 to i386. I've previously looked into that (for amd64 -> armhfp), and it wasn't immediately doable... 4. Disable LTO for i386 package. 5. Disable debug info for i386 package. 6. Drop i386 package. Roman. > All bugs filed during this archive rebuild are listed at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-2025-02-15;users=lu...@debian.org > or: > https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-2025-02-15&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > If you reassign this bug to another package, please mark it as 'affects'-ing > this package. See https://www.debian.org/Bugs/server-control#affects > > If you fail to reproduce this, please provide a build log and diff it with > mine > so that we can identify if something relevant changed in the meantime.
