Static Linux SDK regression on 6.4? Duplicate symbols

Development Package Manager
, ,
1

Hello,

I ran into what looks like a Static Linux SDK regression on 6.4 and filed swiftlang/swift#90196.

Short version: a package that links two vendored BoringSSL copies (swift-nio-ssl + swift-crypto) fails to statically link against musl with duplicate libc++abi symbols (set_new_handler, __cxa_*, terminate, etc). The same package links fine on 6.3.2, and it fails on both Linux and macOS hosts with 6.4, so it points at the toolchain rather than the libraries. Minimal repro and a 6.3-vs-6.4 matrix are in the issue.

Anyone seen this, or know if it belongs somewhere other than swiftlang/swift?

2

Does it work if you switch back to the native build system, i.e. swift build --build-system native ...?

3

He said it was swift-build on the linked issue, better to keep the discussion there.

4

Right, I'm just wondering if the issue is with swift-build or with the SDK itself. If it works with build system native, then it's the SDK that has regressed.

5

And if it's SwiftBuild, this is the first release where it supports Swift SDKs so it maybe just something they've overlooked.

6

Sorry for my late reply folks. It's indeed the new build system causing this error, not a regression on the Static SDK.
I updated the issue description Swift Build 6.4: duplicate libc++abi symbols when statically linking two C++ targets · Issue #90196 · swiftlang/swift · GitHub