Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
Le 03/11/2023 à 21:32, Faidon Liambotis a écrit :
Control: reopen -1
Control: found -1 1:16.0.6-17
Note how /usr/include/wasm32-wasi/c++/v1 is missing.
Test case:
$ apt install clang lld libclang-rt-dev-wasm32 libc++-dev-wasm32
$ cat > hello.cpp <
int main() {
std::cout << "hello world" << std::endl;
return 0;
}
EOF
$ /usr/bin/clang++ -v --target=wasm32-wasi hello.cpp
Only C++ include paths are affected, not C. This almost certainly has to
do with the patch we carry for wasm include paths, that I have
contributed to. Unfortunately I have no time to look into it right now
:( I may find some time in a couple of weeks, but hoping someone else
can take care of it in the meantime :/
I understand better why I didn't get this problem locally:
If you install libc++-dev too, the problem goes away.
because it provides the symlink
/usr/include/c++/v1 -> ../../lib/llvm-16/include/c++/v1
which makes clang happy
but still looking into a different solution
cheers
S
Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
Control: reopen -1
Control: found -1 1:16.0.6-17
This is still not fixed :( Mike's findings still stand:
On Sat, Sep 16, 2023 at 05:53:55AM +0900, Mike Hommey wrote:
> This is a regression from the upgrade to clang 16.
>
> with clang 14:
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/include/wasm32-wasi/c++/v1
> /usr/lib/llvm-14/lib/clang/14.0.6/include
> /usr/local/include
> /usr/include/wasm32-wasi
> /usr/include
> End of search list.
>
> with clang 16:
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/lib/llvm-16/lib/clang/16/include
> /usr/local/include
> /usr/include/wasm32-wasi
> /usr/include
> End of search list.
>
> Note how /usr/include/wasm32-wasi/c++/v1 is missing.
Test case:
$ apt install clang lld libclang-rt-dev-wasm32 libc++-dev-wasm32
$ cat > hello.cpp <
int main() {
std::cout << "hello world" << std::endl;
return 0;
}
EOF
$ /usr/bin/clang++ -v --target=wasm32-wasi hello.cpp
Only C++ include paths are affected, not C. This almost certainly has to
do with the patch we carry for wasm include paths, that I have
contributed to. Unfortunately I have no time to look into it right now
:( I may find some time in a couple of weeks, but hoping someone else
can take care of it in the meantime :/
Best,
Faidon
Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
reassign 1052002 clang-16
affects 1052002 firefox
affects 1052002 firefox-esr
thanks
On Fri, Sep 15, 2023 at 08:19:17PM +0200, Aurelien Jarno wrote:
> 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
> | 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
> | 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 '/<>'
> | make: *** [debian/rules:329: build-arch] Error 2
> | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
> status 2
This is a regression from the upgrade to clang 16.
with clang 14:
#include "..." search starts here:
#include <...> search starts here:
/usr/include/wasm32-wasi/c++/v1
/usr/lib/llvm-14/lib/clang/14.0.6/include
/usr/local/include
/usr/include/wasm32-wasi
/usr/include
End of search list.
with clang 16:
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/llvm-16/lib/clang/16/include
/usr/local/include
/usr/include/wasm32-wasi
/usr/include
End of search list.
Note how /usr/include/wasm32-wasi/c++/v1 is missing.
Mike
Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
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
| 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
| 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 '/<>'
| 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=riscv64=117.0.1-1=1694756702=0
Regards
Aurelien
