swift-sqlcipher – Build Information

Build Information

Failed to build swift-sqlcipher, reference main (bb20ee), with Swift 6.3 for Wasm on 29 Apr 2026 05:30:09 UTC.

Build Command

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

Build Log

========================================
RunAll
========================================
Builder version: 4.70.0
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 bb20eef Update automatic CI submission to use skipbuilder account
Cloned https://github.com/skiptools/swift-sqlcipher.git
Revision (git rev-parse @):
bb20eeff2fb0c2c9e1af2c45ea39e676159be2b1
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-4609320-0":/host -w "$PWD" -e JAVA_HOME="/root/.sdkman/candidates/java/current" -e SPI_BUILD="1" -e SPI_PROCESSING="1" registry.gitlab.com/swiftpackageindex/spi-images:wasm-6.3-latest swift build --swift-sdk swift-6.3-RELEASE_wasm 2>&1
wasm-6.3-latest: Pulling from swiftpackageindex/spi-images
Digest: sha256:d69f4e7582c319245442d62a08b2d7c7fd5a0c0c69f5d2ef11d1530cd8d3329b
Status: Image is up to date for registry.gitlab.com/swiftpackageindex/spi-images:wasm-6.3-latest
Building for debugging...
[0/494] Write sources
[1/494] Compiling aes_tab.c
[2/494] Write swift-version-24593BA9C3E375BF.txt
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/aes/aes_desc.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-RELEASE_wasm.artifactbundle/swift-6.3-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.
[3/494] Compiling aes_desc.c
[3/494] Compiling anubis.c
[3/494] Compiling sosemanuk_test.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-RELEASE_wasm.artifactbundle/swift-6.3-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.
[3/494] Compiling aesni.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/ciphers/aes/aes.c:25:
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-RELEASE_wasm.artifactbundle/swift-6.3-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, \
      |  ^
[3/494] Compiling aes.c
[3/494] Compiling sosemanuk_memory.c
[3/494] Compiling sqlite3.c
[3/494] Compiling blowfish.c
BUILD FAILURE 6.3 wasm