Fail to build (link) executable using generated swift-sdk

[krzyzanowskim]

Description

Building executable with sdk generated with https://github.com/apple/swift-sdk-generator fail on unable to find linker error message

Expected behavior

build

Actual behavior

fatal error

Steps to reproduce

git clone https://github.com/apple/swift-sdk-generator.git
cd swift-sdk-generator
swift run swift-sdk-generator
swift experimental-sdk install Bundles/5.9.2-RELEASE_ubuntu_jammy_aarch64.artifactbundle

mkdir hello-world
cd hello-world
swift-package init --type=executable

swift build --experimental-swift-sdk 5.9.2-RELEASE_ubuntu_jammy_aarch64

error unable to find library. the file at the path exists

ld.lld: error: unable to find library -ld-path=/Users/marcinkrzyzanowski/Library/org.swift.swiftpm/swift-sdks/5.9.2-RELEASE_ubuntu_jammy_aarch64.artifactbundle/5.9.2-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/swift.xctoolchain/usr/bin/ld.lld
clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
error: fatalError

Swift Package Manager version/commit hash

3ce3894

Swift & OS version (output of swift --version ; uname -a)

swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-5.9.2.2.56 clang-1500.1.0.2.5)
Target: arm64-apple-macosx14.0

[MaxDesiatov]

-ld-path became available only in Swift 5.10, I wonder if the issue is reproducible with that version?

[krzyzanowskim]

do you mind giving me a hint on the swift-sdk-generator that is going to produce usable 5.10 to test it on my side?

[MaxDesiatov]

This will generate one with the latest 5.11 snapshot.

swift run swift-sdk-generator --swift-version DEVELOPMENT-SNAPSHOT-2023-12-21-a --swift-branch development

Let me check the right invocation for 5.10 in a moment...

[MaxDesiatov]

Here's one for 5.10:

swift-sdk-generator --swift-version 5.10-DEVELOPMENT-SNAPSHOT-2023-12-21-a --swift-branch swift-5.10-branch

[krzyzanowskim]

Thank you. I confirm that it is not an issue with Swift 5.10 and up.

[MaxDesiatov]

I'll reopen this for now, since apparently we don't check for -ld-path availability cleanly to provide a nice diagnostic message.

[krzyzanowskim]

fair enough. do you think it can be "backported" or just diagnostic and build going to fail?

[MaxDesiatov]

No backporting is possible, since release/5.9 is no longer taking patches IIUC. IMO we should warn that the linker property in toolsets is not supported in 5.9 toolchains and redirect users to pass -use-ld= flag to Swift Driver instead as a workaround.

[krzyzanowskim]

I've meant automatic backport that going to use either -ld-path or -use-ld depends which one suppose to work with the toolchain