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.

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-21, 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 1147573@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna <locutusofborg@debian.org> (supplier of updated llvm-toolchain-21 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 28 Aug 2026 11:47:04 +0200
Source: llvm-toolchain-21
Architecture: source
Version: 1:21.1.8-11
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Gianfranco Costamagna <locutusofborg@debian.org>
Closes: 1147573
Changes:
 llvm-toolchain-21 (1:21.1.8-11) unstable; urgency=medium
 .
   [ Sylvestre Ledru ]
   * d/rules: only enable sccache if the binary actually runs
   * d/control.in: libfuzzer-X.Y-dev now depends on libclang-rt-X.Y-dev.
     -fsanitize=fuzzer links libclang_rt.fuzzer*.a (and
     libclang_rt.ubsan_standalone.a) from the compiler-rt resource
     directory, which lives in libclang-rt-X.Y-dev. As it was only a
     Recommends of libclang-common-X.Y-dev, it was not pulled into build
     chroots and the link failed. Closes: #1147573.
   * d/tests/fuzzer-test: new autopkgtest building a fuzzer with only
     libfuzzer-X.Y-dev installed, to catch this dependency issue.
   * d/debian-llvm-testsuite.bats: don't skip the libFuzzer compilation test
     when the compiler-rt libraries are missing, fail instead.
 .
   [ Gianfranco Costamagna ]
   * Commit Ubuntu patch to git
   * Skip common packages also for stonking
 .
   [ Karl Smeltzer <karl.smeltzer@canonical.com> ]
   * Add patch from Ubuntu: lldb-python-wrapper-exceptions.diff
Checksums-Sha1:
 475c67aeedc14645c9cff77d89d4128a678dd40b 15182 llvm-toolchain-21_21.1.8-11.dsc
 fff03626d7554efaa90e4bfe6566879bdabfee3d 177388 llvm-toolchain-21_21.1.8-11.debian.tar.xz
 6d726c51504bc3b2a789193f89ac88d3b7523950 37384 llvm-toolchain-21_21.1.8-11_amd64.buildinfo
Checksums-Sha256:
 a004546386cefae150f43bfd3d3ee36c04a503b558283f353f16addd3d691059 15182 llvm-toolchain-21_21.1.8-11.dsc
 62f0dbe98616e5d427a4fbd4937b39fff8e1ad23fa12f0b0c6a3d789a213c399 177388 llvm-toolchain-21_21.1.8-11.debian.tar.xz
 393df89645849555a57a3a7c5db30f9772d82de8efe831a65b387415dd9a3601 37384 llvm-toolchain-21_21.1.8-11_amd64.buildinfo
Files:
 905a5814f15465fd15553f49372859da 15182 devel optional llvm-toolchain-21_21.1.8-11.dsc
 d4ab2897c597ae95e5e21d4121bd398f 177388 devel optional llvm-toolchain-21_21.1.8-11.debian.tar.xz
 8d71ae3dbe201cf48f0aeff39a40b014 37384 devel optional llvm-toolchain-21_21.1.8-11_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmqm4JEACgkQfmUo2nUv
G+HQThAAgMTqqJ5k7YDb9RpgWj9fFyDglOCfzU0M778aC8DFmLJOTmIw9Hmt5hCd
/BeEqkAtp91zcZBOX8lLIrA8A90w3mSVlXO9f1raUALR0WqHv7joBVUtVWffcJrb
XPpwSUh7nraua5+3hOUMTAFzIUicyjCS/fJ6Qdaj33n7LJFC0gzh9DBEfgRJ/0vR
cyjKiI7crwXXWRPML/BSyvuSOxbcBCqCFULWvD9fxQb8Es+/Em8u7KGC/l0xiujj
IlyrGTS22gssheeX//16+xlwUVBucHTN1brlF4Q7cpKq7VWmNLaAwHhSxc4wHgb2
9pbkZVLrLI3ts+OGNjPqujUXrgqVzhZjl2iPlkXU2J72ER+fUe8GjyONkjXOxEuS
Uf34YlH7EQ4qMTqjhvUMTcN0bQW5eautUULPXbRYyWqdZijX5roSdP/mU6aN04K3
/pnmUoPxl8JbQxE3DDqmHbQz2iFnJpTua0A+kzxuEYoUhc8d56WZetq5/AXnvu+0
2d8I/VDKnm/5WZSEOjr8n4KS3uDdPF0b9K6xcs52LWhBUqGUSgKDPyo3rxsmYoYE
aHQe6uZ+AKE4Q/gEumugD7dDfr+tGG/vh+T6Ncz+7YwbExwxzKhJs4gdQdojgQ4O
cY1IpFMgRXFRWGJro5V1NU+hAzYjVas1UXiSaxFqbN41irFHZ6E=
=L7tA
-----END PGP SIGNATURE-----

the obsolete libFuzzer.a should be dropped, corresponding patch is on
the 21 branch in the VCS.

Removing the legacy fuzzer.a is a different issue, please open a different bug.
S




Le lundi 14 septembre 2026 à 09:28, Matthias Klose <doko@debian.org> a écrit :

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-21, 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 1147573@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated llvm-toolchain-21 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 14 Sep 2026 09:20:26 +0200
Source: llvm-toolchain-21
Architecture: source
Version: 1:21.1.8-12
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 1147573
Changes:
 llvm-toolchain-21 (1:21.1.8-12) unstable; urgency=medium
 .
   * Stop building, shipping and testing the obsolete libFuzzer.a.
     Closes: #1147573.
Checksums-Sha1:
 41ef9f7af4c405d5f07bacbe561257d040e3a7ae 15207 llvm-toolchain-21_21.1.8-12.dsc
 f0cf9b31167603b857f5983a0645b80bb93bd94a 177324 llvm-toolchain-21_21.1.8-12.debian.tar.xz
 a72a3cf6c94f064c3efc4daeec4eb7c33d89fec0 13744 llvm-toolchain-21_21.1.8-12_source.buildinfo
Checksums-Sha256:
 4471c9a73e5c8ed1366f33042c3a4b2e98bfc4714b064e130fa2f9ae0f71e659 15207 llvm-toolchain-21_21.1.8-12.dsc
 e48dab757dbfe68f0a8c7c75b467605426b8279daf6ce6c62ca3d23b6e714819 177324 llvm-toolchain-21_21.1.8-12.debian.tar.xz
 4ce90a6eb65f697b103f2a602ce8f5a0e1b1d450996c5fc0f27651411285fbba 13744 llvm-toolchain-21_21.1.8-12_source.buildinfo
Files:
 d663c41b60c560825a8626ba32630e62 15207 devel optional llvm-toolchain-21_21.1.8-12.dsc
 bb2f9c4775e1396190d461fb97280527 177324 devel optional llvm-toolchain-21_21.1.8-12.debian.tar.xz
 60f1bdc91787f61446bff6a1e6dbcc5f 13744 devel optional llvm-toolchain-21_21.1.8-12_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmqnuw4QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9frnEACl+9IMxO86fCFSoCa7lrNNewMFBL17D0ox
qFQN7f2FcXzLV4TU3PK9v7UmKDllXk6Sy501xtRQPgR2swVIT79mn8MjGD+EyU00
fCjTQgG2sNJfbYiGXsraMT4ytIWUoGxL0zZlNfQ4H8/8xfRnj1ZZeMmurM1RHXNQ
jhdbSj6NBoFsj1DV6eWv5ooc/Qfd4ndM7qldpcX4tMyGNvMjHI5jrryblke/j40i
tTu8AXCnpll01betl+uA1FQDxYofOcH8VNO8TCfW0uJL7tfKlJA3+PRvwEC9e+LC
ebkFjMZ0xzFTkwe/CGGRVDhzPzy3ZjRtUYPzhJlDP02C8ixrvI3AS+z4MEkZgH6E
7MTIFfi8ist8ly1gNcamaUhyCZJWAam4tiYyctrqXuAwQuVn79Ga7DA60ZOcBuLy
b0xMv4pAhZdHFOMoomW2TP6ITLVsRMI+xFf6WbKisXQfVW8+cE+4bbLKDDoM4kxE
AFO5vMihaW7WkF+V29kj5uqp0oPxALezmPU9MmVzD7VEQ/CRvkRtXuUxPPNfl5vW
/o6vpjmcwikR/vAiJ6UjaWUMKBZuuHQ8uEy7W21KrwN3q+MXWkCshBksCUlcLUSk
HqVQ6CziNEvDlrgbfBICDLzlfVEM8bc1+4woINOxKwjSefWR2ZztI2V4f3jd3u11
9+/bGKRRbQ==
=DbdF
-----END PGP SIGNATURE-----

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 1147573@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru <sylvestre@debian.org> (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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 22 Sep 2026 11:07:11 +0200
Source: llvm-toolchain-23
Architecture: source
Version: 1:23.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Sylvestre Ledru <sylvestre@debian.org>
Closes: 1142996 1147573 1147575 1147981
Changes:
 llvm-toolchain-23 (1:23.1.2-1) unstable; urgency=medium
 .
   * New upstream release
   * d/control.in: libfuzzer-X.Y-dev now depends on libclang-rt-X.Y-dev.
     -fsanitize=fuzzer links libclang_rt.fuzzer*.a (and
     libclang_rt.ubsan_standalone.a) from the compiler-rt resource
     directory, which lives in libclang-rt-X.Y-dev. As it was only a
     Recommends of libclang-common-X.Y-dev, it was not pulled into build
     chroots and the link failed. Closes: #1147573, #1147575.
   * d/debian-llvm-testsuite.bats: don't skip the libFuzzer compilation test
     when the compiler-rt libraries are missing, fail instead.
   * Stop building, shipping and testing the obsolete libFuzzer.a.
     Thanks to Matthias Klose.
   * d/control.in: libmlir-X.Y: remove the provides, conflicts and replaces
     on libmlir-x.y, they are not needed. Thanks to Matthias Klose.
     See #1137244.
   * d/debian-llvm-testsuite.bats: link the fuzzer runtime from the
     compiler-rt resource directory instead of the removed
     /usr/lib/llvm-X.Y/lib/libFuzzer.a, and check that it is present.
   * d/control.in: document that libfuzzer-X.Y-dev is now a dependency
     package: the fuzzer runtime (libclang_rt.fuzzer*.a) and
     FuzzedDataProvider.h come from the compiler-rt resource directory in
     libclang-rt-X.Y-dev, which is what clang links for -fsanitize=fuzzer.
     This also avoids the empty-binary-package lintian warning.
   * d/libmlir-X.Y.install.in, d/libmlir-X.Y.links.in: install the libMLIR
     shared library and the MLIR runtime libraries in /usr/lib/<triplet>
     and keep a compat symlink in /usr/lib/llvm-X.Y/lib so the
     libmlir-X.Y-dev .so symlink and the RUNPATH of the mlir tools keep
     resolving. Thanks to Matthias Klose. Closes: #1142996.
   * 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.
Checksums-Sha1:
 aabeed1fc3fb382593c9d10650aefb2935e20e39 15824 llvm-toolchain-23_23.1.2-1.dsc
 387f99315ac463acfd5791b41e7d04dfbe7bda8d 211605136 llvm-toolchain-23_23.1.2.orig.tar.xz
 2b3209bea4a8d5e5395f48f3babe9de67268b858 190728 llvm-toolchain-23_23.1.2-1.debian.tar.xz
 c7a2e24bb3482f89925afac478c6e85dc09a6e26 39274 llvm-toolchain-23_23.1.2-1_amd64.buildinfo
Checksums-Sha256:
 92de654cb91e9159bc79391cd320983ae8f598d483f5b342e5f5434042e53818 15824 llvm-toolchain-23_23.1.2-1.dsc
 16b28eccb7b7000016c1d4b9afd7680a81dad507d7a28de137a56485c22ae0e4 211605136 llvm-toolchain-23_23.1.2.orig.tar.xz
 818236f01418723e332c8d76702374b10b69dceb1085b12837f38a46d912e572 190728 llvm-toolchain-23_23.1.2-1.debian.tar.xz
 be4138a3f131f48c7bc2d61038281893953585468285e1e7afd4d814532291c1 39274 llvm-toolchain-23_23.1.2-1_amd64.buildinfo
Files:
 1162d1bcd33da55de1dd8cd845d49ee6 15824 devel optional llvm-toolchain-23_23.1.2-1.dsc
 afc063a66ffdb1c3f6937b1e38910abe 211605136 devel optional llvm-toolchain-23_23.1.2.orig.tar.xz
 4ece501cf82bd1f10301f40381539c48 190728 devel optional llvm-toolchain-23_23.1.2-1.debian.tar.xz
 9bdb51ac458d41c71f973ded5cd435e8 39274 devel optional llvm-toolchain-23_23.1.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmqynEwACgkQfmUo2nUv
G+Gs2Q/+OhjNyZOpZY4a6hO4PxH5xsThMVICS6/CL86cbnwxKA2ktQ3VT7Zz+FTh
jtK1C7dseZBK6mHgLIqaRovK3qlkHot9SpAsR+FuglrRPXXmqfRyIaPVXfzB7g+I
kEpdsN2voakKQOeXL4IJ5TplIkk9g9mfLDENoKTFcK2yFpFwhavfHV5nZIqYMQ66
1zi7Jg2dya8zIe/9RcJq3UIW11k2vk1Iak5ka2wsNjghpUC0U5yQ7KzAqCJ7fJNS
5zRXJvR5k0KpMPo9IqNN9se3wqAfbWtsGVwf/BOtlgBhKa5fmOK7oNUtcuH5sWKp
XdJvQjLo398h5zSGNs1gcaWWuf55jfWiIhuMx49Mj7mq0gPv70iGus3vbfR5NTLn
vR2kQisLnLkdYmgZsFbVJsWCZMjXzvUAjAlTRc0mEbZtu86CW0rqbK/PpW+vVgsT
M/ZThYbopLbYs97Q50Nrbb950V6m2gVtx0P0TnApml1fDTqxauj4BZQ2gROmw07q
b9hUY0BAWD4TNhabwEUVO3t0xO/D5I5Ru7vF7dRYyW2Cpu9ppl0OU5nExYEOpjXD
ViQ5K6YFWeKiCmeZ/Bfgaapig0xKlC9Uwps2PTlA93iycMBXwKjNjf9IeTJIGDa6
fnV0EKOEYT70eMWOtvPKXzcvPBI56xR8DTGAq5FzW58bYP/MF/c=
=OStO
-----END PGP SIGNATURE-----

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-22, 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 1147573@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated llvm-toolchain-22 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 25 Jul 2026 18:43:43 +0200
Source: llvm-toolchain-22
Architecture: source
Version: 1:22.1.8-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 1137244 1138702 1141868 1142548 1142778 1147573
Changes:
 llvm-toolchain-22 (1:22.1.8-2) unstable; urgency=medium
 .
   [ Sylvestre Ledru ]
   * d/rules: retry the documentation build serially when sphinx's parallel
     workers die (bare "EOFError" from multiprocessing after a successful
     compile, trixie amd64/arm64 2026-09-02/03)
   * d/rules: set SCCACHE_IDLE_TIMEOUT=0 so the sccache server stays alive for
     the whole build; otherwise it idles out (default 600s) during the quiet
     final-link phase and the libfuzzer step auto-spawns a default-config server
     writing to $HOME/.cache/sccache, which fails with HOME=/nonexistent
   * d/rules: use the shared GCS sccache cache on arm64 too (add arm64 to the
     GCP arch filter)
   * d/rules: Disable sccache on the releases whose glibc is too old for the
     binary the build host provides. /opt/sccache/sccache comes from
     mozilla/sccache's latest release and, on s390x (the only arch without a
     static musl build), needs glibc >= 2.34 since v0.17.0. On focal
     (glibc 2.31) it cannot even start, and the build died at --start-server
     with "version `GLIBC_2.34' not found" in stamps/configure.
   * d/rules: Drop llvm-mt from the install list when it wasn't built.
     Upstream only builds llvm-mt when it detects libxml2 at configure
     time; on Ubuntu focal/arm64 the libxml2 symbol check fails and the
     tool is silently skipped, which made dh_install --fail-missing abort
     on usr/lib/llvm-22/bin/llvm-mt and usr/bin/llvm-mt-22.
   * Add a test for the wasi path detection. Thanks Max Gilmour for the work
     (Closes: #1138702)
   * d/control.in: libfuzzer-X.Y-dev now depends on libclang-rt-X.Y-dev.
     -fsanitize=fuzzer links libclang_rt.fuzzer*.a (and
     libclang_rt.ubsan_standalone.a) from the compiler-rt resource
     directory, which lives in libclang-rt-X.Y-dev. As it was only a
     Recommends of libclang-common-X.Y-dev, it was not pulled into build
     chroots and the link failed. Closes: #1147573.
   * d/debian-llvm-testsuite.bats: don't skip the libFuzzer compilation test
     when the compiler-rt libraries are missing, fail instead.
   * d/libmlir-X.Y.links.in: new, keep a /usr/lib/llvm-X.Y/lib symlink to the
     libMLIR SONAME now installed in /usr/lib/<triplet>. libmlir-X.Y-dev
     ships /usr/lib/llvm-X.Y/lib/libMLIR.so as a relative symlink to it and
     the mlir tools have that directory in their RUNPATH, so both were left
     dangling.
   * d/debian-llvm-testsuite.bats: link the fuzzer runtime from the
     compiler-rt resource directory instead of the removed
     /usr/lib/llvm-X.Y/lib/libFuzzer.a, and check that it is present.
   * d/control.in: document that libfuzzer-X.Y-dev is now a dependency
     package: the fuzzer runtime (libclang_rt.fuzzer*.a) and
     FuzzedDataProvider.h come from the compiler-rt resource directory in
     libclang-rt-X.Y-dev, which is what clang links for -fsanitize=fuzzer.
     This also avoids the empty-binary-package lintian warning.
 .
   [ Talha Can Havadar ]
   * d/p/amdgpu-fix-simulated-trap-continuation-block.diff: cherry-pick
     llvm/llvm-project@9429a1e809fd (PR #174774,
     "[AMDGPU] Fix insertSimulatedTrap to return correct continuation block")
     Fixes a codegen crash on gfx1100/gfx1101/gfx1102 (RDNA3 desktop:
     RX 7900/7800/7700/7600) where clang aborts with
     "fatal error: error in backend: Unsupported instruction : <MCInst NNNN ...>"
     from the AMDGPU AsmPrinter whenever a kernel contains a block that ends in
     llvm.trap() with no successors — an unlowered pseudo reaches the MC layer.
     Notably affects pytorch-rocm 2.12's Loss.hip (FTBFS). Reported upstream as
     llvm/llvm-project#208912. Fix landed on main branch on 2026-01-21 (LLVM 23);
     release/22.x was cut 8 days before and never received it. This cherry-pick
     lets 22.1.x carry the fix without waiting for a 22.1.9 or 22.2.0 point
     release upstream. (Closes: #1141868)
 .
   [ Matthias Klose ]
   * Fix removing RUNPATH, broken in Nov. 2025. Closes: #1142548.
   * Stop building, shipping and testing the obsolete libFuzzer.a.
     Closes: #1147573.
   * Install libmlir shared library in /usr/lib. Closes: #1142778.
   * libmlir: Remove provides, conflicts and replaces. Not needed.
     Closes: #1137244.
Checksums-Sha1:
 441066bfcd3adc8e2d99092a416906683559e6fb 15824 llvm-toolchain-22_22.1.8-2.dsc
 ac4e52194d08bd94088cc58c0a3afd9bc6823eae 183300 llvm-toolchain-22_22.1.8-2.debian.tar.xz
 58bf3666d647d57bc4e001cc8fcba9bf97cc8fe8 39282 llvm-toolchain-22_22.1.8-2_amd64.buildinfo
Checksums-Sha256:
 4df4e778010d03006998ff484996c9d12e7875da129bcaad1cf4e4dbc76abe62 15824 llvm-toolchain-22_22.1.8-2.dsc
 ecee9142cfd59c24ddd97710838cdad4c77558885911f97fa5a310c9e756d842 183300 llvm-toolchain-22_22.1.8-2.debian.tar.xz
 c01220676b53d2f10d65f51afe65d40e1390084263859b04526a3d0c21718f53 39282 llvm-toolchain-22_22.1.8-2_amd64.buildinfo
Files:
 d8b0a2317fb951bb40bd920273db37b9 15824 devel optional llvm-toolchain-22_22.1.8-2.dsc
 9c21723eb868497995784b37aa5c48d1 183300 devel optional llvm-toolchain-22_22.1.8-2.debian.tar.xz
 5772cfc89523702690dbaa2c71d9569e 39282 devel optional llvm-toolchain-22_22.1.8-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmq4uYEACgkQfmUo2nUv
G+F+2w//T1x5wwShiqYbEO5m37NwCnNo5ANLiHFmDotqPRZtWDcJQr7BRX+PMBUh
XaeumbpRBjid960fbOhCeRUO9250iBe3qvpxtX9naL6uhE1hYxFFzTM6HIOJkCc7
Wf7vvHY7p9IFFivvSh+WTPC+dQJveIfEg9h3CH+aauLvKzLnwqUMltc/WPfUTwxE
HnmT+JVQVJNqid74mPCmD3GByBvqewm6+IpLNvXpIPQdPsDQQ+YcxturAnYAei27
ybr1n9jozrdCu4MiCOhSL3Pvi0zFeoq+EaD9ptFPnAD7JdY+Z7pdd6VMqWSPU+uH
7B/omJQXinGMwKTtY/sRWM5nntvkkdS/LDk/kosUl/+xJ3o064o/8flZlnyvxV15
ndKU7K0qjzwAJLI8ML+1H+8sjiSkGPhpY3ZCVhIQJShywfhSPTMS/icCqUFq14pr
8zGAqDjKEMPRRf2YKC8H4SRU40t4k2PRDHJxiczGa65kAqDNIyXdwXjtYPIbSR+C
Cc7J7kwjRZyfJaZaMqdnpEzmqRJJUa0ddIjJNi30CobghdiCwhF5mHUjGmUPgKK/
oYMTlPwTsLX/BW6XLyXyusrADZWa8SVfWUwZZMP9k/ELZgNXcU/3gUDL7GgoWUXx
qflZVIqNhicqtdWTTo81NB1u4SXBJyKApXhSBxw9H4jYuoIiJwk=
=Q/6H
-----END PGP SIGNATURE-----