Your message dated Fri, 20 Oct 2023 07:03:07 +0000
with message-id <e1qtjxh-00ajsy...@fasolo.debian.org>
and subject line Bug#1052002: fixed in llvm-toolchain-16 1:16.0.6-17
has caused the Debian Bug report #1052002,
regarding firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the
wasm compiler. Please fix the problem. Or build with
--without-wasm-sandboxed-libraries
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 ow...@bugs.debian.org
immediately.)
--
1052002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox
Version: 117.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
firefox fails to build from source. From my build log on amd64:
| checking for vpx >= 1.10.0... yes
| checking MOZ_LIBVPX_CFLAGS...
| checking MOZ_LIBVPX_LIBS... -lvpx -lm
| checking for vpx/vpx_decoder.h... yes
| checking for vpx_codec_dec_init_ver... yes
| checking for nasm... /usr/bin/nasm
| checking nasm version... 2.16.01
| checking for the wasm C compiler... /usr/bin/clang
| checking whether the wasm C compiler can be used... yes
| checking the wasm C compiler version... 16.0.6
| checking the wasm C compiler works... yes
| checking the wasm C compiler can find wasi headers... yes
| checking the wasm C linker can find wasi libraries... yes
| checking for the wasm C++ compiler... /usr/bin/clang++
| checking whether the wasm C++ compiler can be used... yes
| checking the wasm C++ compiler version... 16.0.6
| checking the wasm C++ compiler works... yes
| checking the wasm C++ compiler can find wasi headers...
| DEBUG: Creating `/tmp/conftest.t4tbmgsv.cpp` with content:
| DEBUG: | #include <cstring>
| DEBUG: | int
| DEBUG: | main(void)
| DEBUG: | {
| DEBUG: |
| DEBUG: | ;
| DEBUG: | return 0;
| DEBUG: | }
| DEBUG: Executing: `/usr/bin/clang++ --target=wasm32-wasi
/tmp/conftest.t4tbmgsv.cpp -c`
| DEBUG: The command returned non-zero exit status 1.
| DEBUG: Its error output was:
| DEBUG: | /tmp/conftest.t4tbmgsv.cpp:1:10: fatal error: 'cstring' file not
found
| DEBUG: | #include <cstring>
| DEBUG: | ^~~~~~~~~
| DEBUG: | 1 error generated.
| ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix
the problem. Or build with --without-wasm-sandboxed-libraries.
| make[1]: *** [debian/rules:228: stamps/configure-browser] Error 1
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
| make: *** [debian/rules:329: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=firefox&arch=riscv64&ver=117.0.1-1&stamp=1694756702&raw=0
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-16
Source-Version: 1:16.0.6-17
Done: Sylvestre Ledru <sylves...@debian.org>
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-16, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru <sylves...@debian.org> (supplier of updated llvm-toolchain-16
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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 19 Oct 2023 22:37:29 +0200
Source: llvm-toolchain-16
Architecture: source
Version: 1:16.0.6-17
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-t...@lists.alioth.debian.org>
Changed-By: Sylvestre Ledru <sylves...@debian.org>
Closes: 1052002
Changes:
llvm-toolchain-16 (1:16.0.6-17) unstable; urgency=medium
.
* Try to fix the wasm path detection (Closes: #1052002)
Checksums-Sha1:
3ffd65f82dff4a88d9f9735771c47f38a5650682 8275 llvm-toolchain-16_16.0.6-17.dsc
482a1c6e58c0c843c63c9127da1550a972684698 173176
llvm-toolchain-16_16.0.6-17.debian.tar.xz
88db420adb2a61619455b8b12e49c47cf867ec6b 34652
llvm-toolchain-16_16.0.6-17_amd64.buildinfo
Checksums-Sha256:
a2408f2633337b32622ebe8c4772d5c6c84ad74179911f34525a88e715cfc3f0 8275
llvm-toolchain-16_16.0.6-17.dsc
6068358da875b5fc02be85be79f56fab70cb21ca83412406f8dc97da79cae502 173176
llvm-toolchain-16_16.0.6-17.debian.tar.xz
8d5f0c5e77633e505d5dd808337519fd93a53f92881838d2d75c0573997db5d6 34652
llvm-toolchain-16_16.0.6-17_amd64.buildinfo
Files:
44ea32d70c3ad1a8f3154a4a2ef70f40 8275 devel optional
llvm-toolchain-16_16.0.6-17.dsc
fba99dea6bcc9c126f7046b8662c0e08 173176 devel optional
llvm-toolchain-16_16.0.6-17.debian.tar.xz
17d499db26edd4c410114156f95e3c6c 34652 devel optional
llvm-toolchain-16_16.0.6-17_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmUyHeoACgkQfmUo2nUv
G+EuJg//ZvuURgZFw+FQajrDf7TjLsBZhKDOfcRAH55FfQlKO9GnzOe2/X4napiD
wW+V0AGD1uzBMeTbkDDQxHLiFbTh9/gs5hy1YqPyL8QeIL1ekDH4JWzhWIXJqTdS
z2mPDHgUZE0AC0l8sBE9osconqhHPwho5XVXavU6NOlYMHM202MkhIU4Owc9mFKy
ww4qj7QcemaFRmKFT1o7Z4nlWQRJg8TGJHMKWI7a/Z4HiTw6tUoUHOgmI+2BLkdI
P09RoMlhbVvVVaAPlKoe08iCgyOleyWeBdtF+ygUqQnXjA04fn0XwFTQ8PxPaFws
wm3pOQRvDKp1lpqHd+j+69+I0t2OU7ohrA2YVNdkvRA6FvVyRh7EiGkhuMxAIIe0
uoSj1DGAYgGapAdIx1cxCpXCs1unEP92RUyx5EVPHeTw2n3l6tyqpSM45nsYkO0U
KvdOk4JSNStFV1/kyZ/G/gII1rvX6yBmX1kOAsSAdd6OlWbzF+fP/4U5Fm5ULu+i
z626AtIx7rLJDurPefr2LH8n0lsj+GSIR2zIHPA5hqVBeRh+LyV2WTHnBWTaV4jn
3oFDBpmcBLB7OWnQeM3OdoMItQikDyk35efevmEZyImT4TB7LwHbp+Q3M2cCQIzd
d6JIdC86NYY4+iOuysFjFnw4Yla7FllMAbWw+kEhZ5zg9RMK7Pw=
=EKe0
-----END PGP SIGNATURE-----
--- End Message ---