Bug#1085853: libclang-rt-19-dev: please re-enable for 32-bit archs

Emilio Pozuelo Monfort pochu at debian.org
Fri Oct 25 10:55:32 BST 2024


Control: severity -1 serious

Hi,

On Tue, 22 Oct 2024 19:01:02 -0400 Andres Salomon <dilinger at queued.net> wrote:
> Package: libclang-rt-19-dev
> Version: 1:19.1.2-1
> 
> libclang-rt-19-dev currently isn't built for armhf, which is keeping 
> chromium (which recently switched away from clang 16) from migrating to 
> trixie. When I asked on IRC about why it wasn't built for armhf, I was 
> pointed to this commit, where libclang-rt-*dev stops being built for 
> 32-bit architectures:
> 
> https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/1a18aa1aa6e9fc698868fd22a99ea875f3efb20a
> 
> This was originally added to fix clang 18 FTBFS. The workaround has 
> since been removed from the 18 branch, but that hasn't been merged into 
> the 19 branch. I'd appreciate if someone could merge the removal into 
> the 19 branch so chromium's build-deps on armhf can be satisfied.

With my RT hat on, I'm bumping this to RC, since it prevents chromium updates 
from reaching testing (most of which are security updates) and it also makes it 
harder to remove llvm 16 from trixie. We don't want chromium from going back to 
LLVM 16, so this is a blocker and RC.

Cheers,
Emilio



More information about the Pkg-llvm-team mailing list