Unable to create Bookworm SDK (unclear documentation)

[dscreve]

Just enter the following command :

$> swift run swift-sdk-generator make-linux-sdk --with-docker --from-container-image swift:6.0.3-bookworm:latest --sdk-name 6.0.3-bookworm

Result :
warning: failed to retrieve search paths with pkg-config; maybe pkg-config is not installed
warning: couldn't find pc file for sqlite3
Building for debugging...
[1/1] Write swift-version--58304C5D6DBC2206.txt
Build of product 'swift-sdk-generator' complete! (2.18s)
2025-02-25T19:48:51+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Downloading required toolchain packages...
2025-02-25T19:48:51+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Using downloaded artifacts from cache
2025-02-25T19:48:51+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Launching a container to extract the Swift SDK for the target triple...
Error: process exited non-zero: exit(125)

[xtremekforever]

Looks like you have a typo in your tag name. It should be:

--from-container-image swift:6.0.3-bookworm

Without the last :latest part.

[MaxDesiatov]

Hi @dscreve, would you be able to confirm that the issue is resolved for you when using the proposed tag name?

[dscreve]

Hello,

This works fine, but If I use an amd64 image on Mac M1, it does not works. Only arm64 image works.

I have created an amd64 Linux image from with this docker file :
FROM swift:6.0.3-bookworm

Then, use this command :
% swift run swift-sdk-generator make-linux-sdk --with-docker --from-container-image dlta-swift-docker-amd64 --sdk-name 6.0.3-bookworm-amd64

And I have the following error messages :
Building for debugging...
[1/1] Write swift-version--58304C5D6DBC2206.txt
Build of product 'swift-sdk-generator' complete! (0.27s)
2025-02-27T14:37:30+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Downloading required toolchain packages...
2025-02-27T14:37:30+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Using downloaded artifacts from cache
2025-02-27T14:37:30+0100 info org.swift.swift-sdk-generator : [SwiftSDKGenerator] Launching a container to extract the Swift SDK for the target triple...
Error: process exited non-zero: exit(125)

If I go into the Bundles/6.0.3-bookworm-amd64.artifactbundle/6.0.3-bookworm-amd64 directory, I have a directory named
aarch64-unknown-linux-gnu.
So, it seems to be a problem with target architecture.

And I don't know if Glibc has been selected instead of Musl

David

[xtremekforever]

@dscreve you have to provide the --target param as well: --target x86_64-unknown-linux-gnu

If your container arch doesn't match the target arch it will certainly have issues. So, the full command should be:

swift run swift-sdk-generator make-linux-sdk --with-docker --from-container-image dlta-swift-docker-amd64 --target x86_64-unknown-linux-gnu --sdk-name 6.0.3-bookworm-amd64

[dscreve]

Thanks ! this works fine for sdk creation.

What are the accepted values for --parameters ? readme.md documentation seems to be outdated and incomplete.

Now, I try to compile a project on my Mac using x86-64 and aarch64 SDK.

I get some warnings :
warning: Could not read SDKSettings.json for SDK at: /Users/dscreve/Library/org.swift.swiftpm/swift-sdks/6.0.3-bookworm-amd64.artifactbundle/6.0.3-bookworm-amd64/x86_64-unknown-linux-gnu/ubuntu-jammy.sdk

warning: libc not found for 'x86_64-unknown-linux-gnu'; C stdlib may be unavailable

And when compiling, I get compilation errors :
9 | import CryptoKit
| `- error: no such module 'CryptoKit'

any idea how to fix it ?

David

[xtremekforever]

Um....I think that CryptoKit is not available on Linux platforms...am I correct @MaxDesiatov ?

[MaxDesiatov]

You should use swift-crypto instead, which will switch between CryptoKit and the OSS shims over BoringSSL, depending on the OS you're targeting.

[euanh]

You can ignore these warnings:

warning: Could not read SDKSettings.json for SDK at: /Users/dscreve/Library/org.swift.swiftpm/swift-sdks/6.0.3-bookworm-amd64.artifactbundle/6.0.3-bookworm-amd64/x86_64-unknown-linux-gnu/ubuntu-jammy.sdk

#185 should fix this warning

warning: libc not found for 'x86_64-unknown-linux-gnu'; C stdlib may be unavailable

swiftlang/swift#76545 should fix this warning

[dscreve]

You should use swift-crypto instead, which will switch between CryptoKit and the OSS shims over BoringSSL, depending on the OS you're targeting.

You are right !

I will fix this.

[MaxDesiatov]

Thanks for checking! I'll keep this open as a reminder for documentation improvements.