swift-sqlcipher – Build Information

Build Information

Failed to build swift-sqlcipher, reference main (882c3d), with Swift 6.3 for Wasm on 9 Sep 2026 03:44:18 UTC.

Build Command

bash -c docker run --pull=always --rm -v "checkouts-54344847-0":/host -w "$PWD" -e JAVA_HOME="/root/.sdkman/candidates/java/current" -e SPI_BUILD="1" -e SPI_PROCESSING="1" registry.gitlab.com/saguaro1/spi-images:wasm-6.3-latest swift build --swift-sdk swift-6.3.2-RELEASE_wasm 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 5.0.2
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/skiptools/swift-sqlcipher.git
Reference: main
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/skiptools/swift-sqlcipher
 * branch            main       -> FETCH_HEAD
 * [new branch]      main       -> origin/main
HEAD is now at 882c3d6
Cloned https://github.com/skiptools/swift-sqlcipher.git
Revision (git rev-parse @):
882c3d63a2677ccada1e841e7f15ecc6222a6b79
SPI manifest file found: $PWD/.spi.yml
SUCCESS checkout https://github.com/skiptools/swift-sqlcipher.git at main
========================================
Build
========================================
Selected platform:         wasm
Swift version:             6.3
Building package at path:  $PWD
https://github.com/skiptools/swift-sqlcipher.git
Running build ...
bash -c docker run --pull=always --rm -v "checkouts-54344847-0":/host -w "$PWD" -e JAVA_HOME="/root/.sdkman/candidates/java/current" -e SPI_BUILD="1" -e SPI_PROCESSING="1" registry.gitlab.com/saguaro1/spi-images:wasm-6.3-latest swift build --swift-sdk swift-6.3.2-RELEASE_wasm 2>&1
wasm-6.3-latest: Pulling from saguaro1/spi-images
Digest: sha256:e92e38b97676c18adb57b57429ddfb766786102cb50cb918e0d9e8055d05b35d
Status: Image is up to date for registry.gitlab.com/saguaro1/spi-images:wasm-6.3-latest
Building for debugging...
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/blowfish.c:7:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
1 error generated.
[0/494] Compiling blowfish.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/encauth/ocb3/ocb3_decrypt.c:8:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
1 error generated.
[0/494] Compiling ocb3_decrypt.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/aes/aesni.c:10:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
1 error generated.
[0/494] Compiling aesni.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/camellia.c:9:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
1 error generated.
[0/494] Compiling camellia.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/anubis.c:10:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
1 error generated.
[0/494] Compiling anubis.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/des.c:3:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_private.h:4:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt.h:89:
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/headers/tomcrypt_argchk.h:10:
/root/.swiftpm/swift-sdks/swift-6.3.2-RELEASE_wasm.artifactbundle/swift-6.3.2-RELEASE_wasm/wasm32-unknown-wasip1/WASI.sdk/include/wasm32-wasip1/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, \
      |  ^
[0/494] Compiling des.c
[0/494] Compiling ocb3_encrypt.c
[0/494] Compiling cast5.c
BUILD FAILURE 6.3 wasm