Your message dated Sun, 25 Oct 2026 08:22:41 +0000
with message-id <[email protected]>
and subject line Bug#1149144: fixed in llvm-toolchain-23 1:23.1.4-2
has caused the Debian Bug report #1149144,
regarding libc++-23-dev-wasm32: please provide both EH and non-EH variants
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.)
--
1149144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149144
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libc++-23-dev-wasm32
Version: 1:23.1.2-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Since LLVM 23.1.0, Clang supports separate C++ standard library
variants for WebAssembly with and without exception handling. [1][2]
[1] [WebAssembly] Clang support for exception-based lookup paths -
#185775#185775 https://github.com/llvm/llvm-project/pull/185775
[2] [WebAssembly] Move __cpp_exception to libunwind
https://github.com/llvm/llvm-project/pull/185770
The Clang driver selects the appropriate variant depending on whether
-fwasm-exceptions is specified.
Currently, however, libc++-23-dev-wasm32 is built with:
-DLIBCXX_ENABLE_EXCEPTIONS:BOOL=OFF
-DLIBCXXABI_ENABLE_EXCEPTIONS:BOOL=OFF
-DLIBCXXABI_USE_LLVM_UNWINDER:BOOL=OFF
As a result, the Debian WASM libc++ package provides only
the non-exception-enabled variant.
To make use of the exception-based lookup paths provided by Clang,
both the exception-enabled (EH) and non-exception-enabled (non EH)
variants of libc++ and libc++abi need to be built and installed in the
locations expected by the Clang WebAssembly driver.
* What was the outcome of this action?
When -fwasm-exceptions is enabled, the Clang driver is already able to
select the exception-enabled C++ standard library variant; otherwise it
selects the non-exception-enabled variant.
However, Debian currently does not provide the exception-enabled variant
in libc++-23-dev-wasm32, so C++ applications using WebAssembly exception
handling cannot use the corresponding libc++ runtime from the Debian
package.
Please consider providing both variants in the WASM libc++/libc++abi
packages.
Best Regards,
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-23
Source-Version: 1:23.1.4-2
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: Fri, 23 Oct 2026 10:00:00 +0200
Source: llvm-toolchain-23
Architecture: source
Version: 1:23.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 1149144 1151646
Changes:
llvm-toolchain-23 (1:23.1.4-2) unstable; urgency=medium
.
* libmlir-23-dev: drop the Conflicts against the libmlir-x.y-dev virtual
package, everything is installed under /usr/lib/llvm-23 so it is
co-installable with the other versions (see #1142996)
* d/debian-llvm-testsuite.bats: add two tests covering the location of
the MLIR libraries in /usr/lib/<triplet> and the co-installability
(see #1142996)
* Fix the FTBFS with doxygen 1.17: it does not generate jquery.js anymore,
only replace it by the symlink to libjs-jquery when it exists.
(Closes: #1151646)
* libc++-23-dev-wasm32, libc++abi-23-dev-wasm32: also build and ship an
exception-enabled variant of libc++, libc++abi and libunwind, in
/usr/lib/wasm32-wasi/eh, used by clang with -fwasm-exceptions. Built
like wasi-sdk does (exnref, so -mllvm -wasm-use-legacy-eh=false, and
-lunwind needed at link time). The headers are identical, so shared.
The non-exception variant stays in the existing location.
d/p/wasm/wasm-sysroot-usr.diff: keep the eh/noeh include directory
lookup added upstream.
d/p/wasm/libunwind-wasm-no-declspec.diff: fix the libunwind build for
wasm (upstream PR 168449, also used by wasi-sdk).
Add an autopkgtest. (Closes: #1149144)
Checksums-Sha1:
224ebe0db7e643e182fa522de66e0f030ca2e2b5 15321 llvm-toolchain-23_23.1.4-2.dsc
e5c65b39547768f2d862c30c7c8cc469964c12e6 191636
llvm-toolchain-23_23.1.4-2.debian.tar.xz
fd89fb49e83af260deb940da88016e9ed7099759 38388
llvm-toolchain-23_23.1.4-2_amd64.buildinfo
Checksums-Sha256:
215941b1256438c97ed4106f13a02fd356bb745406e3ac8b5adb229d6a5bd90c 15321
llvm-toolchain-23_23.1.4-2.dsc
f6c9eb34cc5a4d7c9ad049ab1e75275e2485bfb3449a4665419a3caa3fb42b67 191636
llvm-toolchain-23_23.1.4-2.debian.tar.xz
fca8b6588606b5e550a7c97524d2df7884a1e6cd3d8b96745db10f50eafd8694 38388
llvm-toolchain-23_23.1.4-2_amd64.buildinfo
Files:
7bae6eb8ed0aa088647bf5ee7d66e24e 15321 devel optional
llvm-toolchain-23_23.1.4-2.dsc
790db58b7efa14730ac82c022c25b4c5 191636 devel optional
llvm-toolchain-23_23.1.4-2.debian.tar.xz
27bdd71a7950d3a5fb007b1d62bcaacc 38388 devel optional
llvm-toolchain-23_23.1.4-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmrdt/IACgkQfmUo2nUv
G+GhNQ/+NqPdHRQ+oVAp6Vwg5Q12EltUrLSFdta4aXiY4wg+02XuiGFR6FQQMDvD
C+sLL5G5tEQiWnjZnFiCBYWp3SVHtRsRij0/zH+g/Jd3pc1wW5UtUkqbY7A70mA3
MGEvoUpL7cxjhrhJ49hgxG6Smp3tDaMfRdC+Y+UNJ1XjXovPObl54J/KwOJd8Bni
rTI7ZoBlDinIRwUFxV2RIzf5gYoJLmZehgAMs8iLqbtsDp8gYdDpLIVMwgT/gx2a
2V17MYaXcKfPcot3UFji276kWFJK9UZb7cDVyLanE/Hu/Lk/SxpqQP1MQr0AoOAf
GWs9Kwg5HrQ4/1zKDjpeGD2UUUUcNBxrlOvdo69wPvxQfDl58ecNf4DeD/iuIYKk
CpCygZzh9EKD4BPWdMLn+ti+MWLvNW0vqBJVHF8VKoJYSrZT1k84rL1Fm1BadyF6
pm80o2i0LKO+cBL79pPbYziBpSU23HCnbMYkXRrUTpb/tTvpE/+YbRN7hyST7ohi
J16QqtrfYgA9Bkh+ym78M5Wu+6lIge+YDbtJ8wELrK2zoJqKkrPS9rxaGoh16sZP
W2rVgfCmu/EzO/tOfQAM8yOF+xWfzhYoOXXVpJzuY/SFgi6ALP2SooEr5fBkpu+e
4FbmxnoJjQKu9vrIPH4jLQe188YisNTKJhdUSGmuc2YLeGVoUnQ=
=Jn+A
-----END PGP SIGNATURE-----
pgpdeARvKP42L.pgp
Description: PGP signature
--- End Message ---
