The Swift Package Index logo.Swift Package Index

Build Information

Failed to build scrypt, reference 0.1.1 (0a1ac9), with Swift 6.2 for Wasm on 18 Jun 2025 04:36:28 UTC.

Build Command

bash -c docker run --pull=always --rm -v "checkouts-4609320-3":/host -w "$PWD" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasi 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 4.64.0
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/v57/scrypt.c.git
Reference: 0.1.1
Initialized empty Git repository in /host/spi-builder-workspace/.git/
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
From https://github.com/v57/scrypt.c
 * tag               0.1.1      -> FETCH_HEAD
HEAD is now at 0a1ac94 Added non-sse2 cpu support
Cloned https://github.com/v57/scrypt.c.git
Revision (git rev-parse @):
0a1ac944808cd667a0c2e2457a4729dcdd447085
SUCCESS checkout https://github.com/v57/scrypt.c.git at 0.1.1
========================================
Build
========================================
Selected platform:         wasm
Swift version:             6.2
Building package at path:  $PWD
https://github.com/v57/scrypt.c.git
Running build ...
bash -c docker run --pull=always --rm -v "checkouts-4609320-3":/host -w "$PWD" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasi 2>&1
wasm-6.2-latest: Pulling from finestructure/spi-images
Digest: sha256:44384f43f933eaa0f42803e9ef7c3d8388c5841ccc831a15a5edf63d8c273423
Status: Image is up to date for registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest
Building for debugging...
[0/11] Compiling scrypt entropy.c
[1/11] Compiling scrypt insecure_memzero.c
[2/11] Compiling scrypt crypto_scrypt_smix_sse2.c
[3/11] Compiling scrypt warnp.c
In file included from /host/spi-builder-workspace/scrypt/readpass.c:1:
/root/.swiftpm/swift-sdks/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-05-30-a_wasm.artifactbundle/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-05-30-a_wasm/wasm32-unknown-wasi/WASI.sdk/include/wasm32-wasi/signal.h:2:2: error: "wasm lacks signal support; to enable minimal signal emulation, compile with -D_WASI_EMULATED_SIGNAL and link with -lwasi-emulated-signal"
    2 | #error "wasm lacks signal support; to enable minimal signal emulation, \
      |  ^
/host/spi-builder-workspace/scrypt/readpass.c:4:10: fatal error: 'termios.h' file not found
    4 | #include <termios.h>
      |          ^~~~~~~~~~~
2 errors generated.
[4/11] Compiling scrypt readpass.c
[4/11] Compiling scrypt humansize.c
[4/11] Compiling scrypt sha256.c
[4/11] Compiling scrypt crypto_scrypt.c
In file included from /host/spi-builder-workspace/scrypt/getopt.c:6:
In file included from /host/spi-builder-workspace/scrypt/getopt.h:5:
/root/.swiftpm/swift-sdks/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-05-30-a_wasm.artifactbundle/swift-6.2-DEVELOPMENT-SNAPSHOT-2025-05-30-a_wasm/wasm32-unknown-wasi/WASI.sdk/include/wasm32-wasi/setjmp.h:13:2: error: Setjmp/longjmp support requires Exception handling support, which is [not yet standardized](https://github.com/WebAssembly/proposals?tab=readme-ov-file#phase-3---implementation-phase-cg--wg). To enable it, compile with `-mllvm -wasm-enable-sjlj` and use an engine that implements the Exception handling proposal.
   13 | #error Setjmp/longjmp support requires Exception handling support, which is [not yet standardized](https://github.com/WebAssembly/proposals?tab=readme-ov-file#phase-3---implementation-phase-cg--wg). To enable it, compile with `-mllvm -wasm-enable-sjlj` and use an engine that implements the Exception handling proposal.
      |  ^
1 error generated.
[4/11] Compiling scrypt getopt.c
[4/11] Compiling scrypt asprintf.c
[4/11] Compiling scrypt crypto_scrypt_smix.c
BUILD FAILURE 6.2 wasm