Skip to content

Commit 9e987fe

Browse files
committed
Set the C target to wasm32-wasi rather than wasm32
We need at least a partial C stdlib anyway, so there's no real difference going ahead and linking wasm32-wasi on the C side vs only on the Rust side. This fixes compilation on Debian testing with OS packages installed.
1 parent 92fc0ad commit 9e987fe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

genbindings.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -509,9 +509,9 @@ if [ "$2" = "false" -a "$(rustc --print target-list | grep wasm32-wasi)" != "" ]
509509
echo "int main() {}" > genbindings_wasm_test_file.c
510510
if clang -nostdlib -o /dev/null --target=wasm32-wasi -Wl,--no-entry genbindings_wasm_test_file.c > /dev/null 2>&1; then
511511
# And if it does, build a WASM binary without capturing errors
512-
export CFLAGS_wasm32_wasi="$BASE_CFLAGS -target wasm32 -O1"
512+
export CFLAGS_wasm32_wasi="$BASE_CFLAGS -target wasm32-wasi -O1"
513513
RUSTFLAGS="$BASE_RUSTFLAGS -C opt-level=1 --cfg=test_mod_pointers" cargo build $CARGO_BUILD_ARGS -v --target=wasm32-wasi
514-
export CFLAGS_wasm32_wasi="$BASE_CFLAGS -fembed-bitcode -target wasm32 -Oz"
514+
export CFLAGS_wasm32_wasi="$BASE_CFLAGS -fembed-bitcode -target wasm32-wasi -Oz"
515515
RUSTFLAGS="$BASE_RUSTFLAGS -C embed-bitcode=yes -C opt-level=z -C linker-plugin-lto -C lto" CARGO_PROFILE_RELEASE_LTO=true cargo build $CARGO_BUILD_ARGS -v --release --target=wasm32-wasi
516516
else
517517
echo "Cannot build WASM lib as clang does not seem to support the wasm32-wasi target"

0 commit comments

Comments
 (0)