Swift Package Index

Build Information

Failed to build swift-sqlcipher, reference 1.7.0 (02649e), with Swift 6.2 for Wasm on 8 Dec 2025 21:18:47 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/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasip1 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 4.68.0
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/skiptools/swift-sqlcipher.git
Reference: 1.7.0
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
 * tag               1.7.0      -> FETCH_HEAD
HEAD is now at 02649e1
Cloned https://github.com/skiptools/swift-sqlcipher.git
Revision (git rev-parse @):
02649e1dc7e3d8905eac2aaf2773bd220cb5cff2
SPI manifest file found: $PWD/.spi.yml
SUCCESS checkout https://github.com/skiptools/swift-sqlcipher.git at 1.7.0
========================================
Build
========================================
Selected platform:         wasm
Swift version:             6.2
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/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasip1 2>&1
wasm-6.2-latest: Pulling from finestructure/spi-images
Digest: sha256:302e3f347c593123f3d337e3da1bfe6e802bb8867614e9dfa745c72e13ca8eeb
Status: Image is up to date for registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest
warning: multiple Swift SDKs match target triple `wasm32-unknown-wasip1` and host triple x86_64-unknown-linux-gnu, selected one at /root/.swiftpm/swift-sdks/swift-6.2-RELEASE_wasm.artifactbundle/swift-6.2-RELEASE_wasm/wasm32-unknown-wasip1/swift-sdk.json
warning: 'spi-builder-workspace': found 1 file(s) which are unhandled; explicitly declare them as resources or exclude from the target
    /host/spi-builder-workspace/Sources/SQLiteDB/PrivacyInfo.xcprivacy
Building for debugging...
[0/494] Compiling aes_tab.c
In file included from /host/spi-builder-workspace/Sources/SQLCipher/libtomcrypt/encauth/chachapoly/chacha20poly1305_decrypt.c:4:
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.2-RELEASE_wasm.artifactbundle/swift-6.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.
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.2-RELEASE_wasm.artifactbundle/swift-6.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.
[1/494] Compiling chacha20poly1305_decrypt.c
[1/494] Compiling aes_desc.c
[1/494] Compiling chacha20poly1305_done.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.2-RELEASE_wasm.artifactbundle/swift-6.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.
[1/494] Compiling aes.c
[1/494] Compiling chacha20poly1305_add_aad.c
[1/494] Compiling ccm_test.c
[1/494] Compiling ccm_reset.c
[1/494] Write swift-version-24593BA9C3E375BF.txt
BUILD FAILURE 6.2 wasm