Your message dated Fri, 09 Oct 2026 21:50:05 +0000
with message-id <[email protected]>
and subject line Bug#1147575: fixed in llvm-toolchain-23 1:23.1.3-1
has caused the Debian Bug report #1147575,
regarding packaging of the fuzzer libraries is broken with LLVM 21, 22 and 23
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:llvm-toolchain-23
Version: 1:23.1.1-2
Severity: serious
Tags: sid forky
As seen in the vbox-tools upload to migrate from LLVM 19 to 21, the
fuzzer libraries are not used anymore (or not found) when built with
LLVM 21. You can reproduce that when building with the unversioned clang:
[...]
LD tests/vb2_keyblock_fuzzer
clang -o
/packages/tmp/vboot-utils-0~R106-15054.B+dfsg/build/tests/vb2_keyblock_fuzzer
-Wl,-z,relro -Wl,-z,now -Wl,--gc-sections -pie -Xlinker
--allow-multiple-definition -fsanitize=fuzzer
/packages/tmp/vboot-utils-0~R106-15054.B+dfsg/build/tests/vb2_keyblock_fuzzer.o
/packages/tmp/vboot-utils-0~R106-15054.B+dfsg/build/vboot_fw.a -lrt -luuid
/usr/bin/x86_64-linux-gnu-ld.bfd/usr/bin/x86_64-linux-gnu-ld.bfd: cannot
find : cannot find
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer.a:
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer.a:
No such file or directory
No such file or directory
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer_interceptors.a:
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer_interceptors.aNo
such file or directory:
No such file or directory
/usr/bin/x86_64-linux-gnu-ld.bfd/usr/bin/x86_64-linux-gnu-ld.bfd: cannot
find : cannot find
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.ubsan_standalone.a/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.ubsan_standalone.a:
: No such file or directoryNo such file or directory
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer.a:
No such file or directory
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find
/usr/lib/llvm-21/lib/clang/21/lib/x86_64-pc-linux-gnu/libclang_rt.fuzzer_interceptors.a:
No such file or directory
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make[2]: *** [Makefile:1156:
/packages/tmp/vboot-utils-0~R106-15054.B+dfsg/build/tests/cgpt_fuzzer]
Error 1
make[2]: *** Waiting for unfinished jobs....
So apparently building and shipping Debian's own libFuzzer.a is not good
enough anymore.
Two solutions here:
- stop building the libfuzzer-N-dev package
- Ship the libclang_rt.fuzzer.a (and maybe other) libraries.
This is seen with LLVM 21, 22 and 23.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-23
Source-Version: 1:23.1.3-1
Done: Sylvestre Ledru <[email protected]>
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-23, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru <[email protected]> (supplier of updated llvm-toolchain-23
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 06 Oct 2026 17:35:24 +0200
Source: llvm-toolchain-23
Architecture: source
Version: 1:23.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 1142996 1147575 1147981
Changes:
llvm-toolchain-23 (1:23.1.3-1) unstable; urgency=medium
.
* New upstream release
* libmlir-23: also expose libMLIR.so and the MLIR runtime libraries
under /usr/lib/<triplet>/, they were only shipped in the private
/usr/lib/llvm-23/lib directory. (Closes: #1142996)
* libfuzzer-23-dev: depend on libclang-rt-23-dev. -fsanitize=fuzzer
links libclang_rt.fuzzer, libclang_rt.fuzzer_interceptors and
libclang_rt.ubsan_standalone, which are shipped by libclang-rt-23-dev
and were only a Recommends of libclang-common-23-dev, so they are
missing in a build chroot. (Closes: #1147575)
* d/rules: pass LLVM_ENABLE_PER_TARGET_RUNTIME_DIR through to the stage 2
build. Only the stage 1 build and the runtimes sub-builds had it set to
OFF, so the installed clang driver defaulted to the per-target layout
(lib/clang/23/lib/x86_64-pc-linux-gnu) while compiler-rt is installed in
lib/clang/23/lib/linux. "clang -print-runtime-dir" pointed at a
non-existent directory and the error messages for a missing
libclang-rt-23-dev named the wrong path.
* lldb: move the system-wide lldbinit from /etc/lldb to /etc/lldb-23.
The unversioned path made liblldb-23 conflict with liblldb-22 on
/etc/lldb/lldbinit. (Closes: #1147981)
* Fix some lintian warnings:
- d/copyright: add the missing License field to the
clang/lib/Headers/cuda_wrappers/* paragraph and add the missing
BSD-3-Clause license paragraph
- d/patches/unbreak-arhmf.patch: remove, not in the series and
fixed upstream
- d/source/lintian-overrides: drop mismatched source-is-missing
overrides already covered by llvm/test/* and lldb/test/*
- d/clang-X.Y-doc.lintian-overrides.in: fix the alien
privacy-breach-generic tag (stray colon)
- d/clang-tools-X.Y.lintian-overrides.in: manpage-has-useless-whatis-entry
was renamed to useless-whatis-entry
- d/compat, d/control.in: use debhelper-compat (= 11) instead
- d/lldb-X.Y.postinst.in: remove, lldb-23 ships no shared library
so calling ldconfig is unneeded
- d/NEWS: use a version present in the changelog
(debian-news-entry-has-unknown-version)
- d/libmlir-X.Y.lintian-overrides.in: override
package-name-doesnt-match-sonames
- d/libc++1.lintian-overrides.in, d/libllvmX.Y.lintian-overrides.in:
override lacks-unversioned-link-to-shared-library, the .so link
is shipped by the -dev package
Checksums-Sha1:
bb3907ba3e7aef967f1a2afa6f24bb9517779490 15828 llvm-toolchain-23_23.1.3-1.dsc
f23896d7017cbd0f0f51ad2f6754a4305231a297 211589888
llvm-toolchain-23_23.1.3.orig.tar.xz
6c345be62302b0e806651c5c2518c9582929cc67 190904
llvm-toolchain-23_23.1.3-1.debian.tar.xz
38ae4f4500c38f386059433fa5bd72666d7fd4d6 39232
llvm-toolchain-23_23.1.3-1_amd64.buildinfo
Checksums-Sha256:
bddfad2180393d0b3ddbc4c9715030fb1f6bb45b238dd9b26a0cb793c5f6c7c5 15828
llvm-toolchain-23_23.1.3-1.dsc
821cc30695902c4b7e86d0e59ceaf4877ab931b66152e1793c4b19541c9ea319 211589888
llvm-toolchain-23_23.1.3.orig.tar.xz
320401b6a6e4725285ade4aafab31079b7d841ab179644d43007c9da6f561421 190904
llvm-toolchain-23_23.1.3-1.debian.tar.xz
5fc2215eea75cb61a5a8ef5783064d482757eca552bcfb9b23074ccab6054e46 39232
llvm-toolchain-23_23.1.3-1_amd64.buildinfo
Files:
eaca859201966a32594ace3c165a9a0f 15828 devel optional
llvm-toolchain-23_23.1.3-1.dsc
12dcc98f8103a553e1d1d0e9002d041d 211589888 devel optional
llvm-toolchain-23_23.1.3.orig.tar.xz
eb9f2dd4a825994d1cea14becaab4c10 190904 devel optional
llvm-toolchain-23_23.1.3-1.debian.tar.xz
6abe2d3360ba6f7df6d118d91032fbbd 39232 devel optional
llvm-toolchain-23_23.1.3-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmrJXPkACgkQfmUo2nUv
G+Enlg/7BitMwaLLCPYDQL5Ja/hTQTY/IoGZdzsqounO34vzoGkCl8EBvuXudTR8
868thqjLH4OWXuLzkEZsf13FbIYmSEEki+LHnCYBpxX/6zqV0UzQcARpBLIh4Q0A
q6X9RrbpEmMrs5kB3vTzqRorK8Ewr4jD8mBmwEu8tTamSzk224maGjR3V/iAiPYT
Nmbfk1eZoK5ukaYra0i5qon/K7Vs0p97/RAlob+pYiEz4psFjaP8P02dEfGPnGpe
xjnKbj4/uzl3QOEmKrE6ioksnZK5I1OKCi/dQOUgKlEKeFcNnY2NolY88D/kljXl
UK5/joc61D67mMipvM5XARa0x25VSyruaKU0Mahx6iYLP++AZic8+fzf+tOW7sL0
YueP9Q8T0iLP0JDv36h04LwO230RJ4keH0q8FINuO8z1ZLkX/bpZ0FPIe+wtfNM4
TprnX7Y3imfWLMxReaPuvxlsi1KGUWfURzq8gRWgVdz+7IQCm3HAoWg6Es0zLBU6
F5X1l+bmwqxdQqGlBPEsVOTOnWPUblthY8yGT3JYK72PZ5wTq46Ts6sjtmOA2Tn0
L6qyfpJPoas1Hj6xvgE+D1Wm6US7EfNS78Zhb4lcR1T1twvnhteGC2aKAMEJl1ol
a0foB9JL1+7+TLEi2XzS+8u53kJlwFz6DpBMZ2difixbwJ9hw0s=
=ZFgz
-----END PGP SIGNATURE-----
pgpxxdvfCy_dR.pgp
Description: PGP signature
--- End Message ---
