forked from swiftlang/swift
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wasm lacks signal support #5592
Comments
Solved by adding the them to my Package.swift cSettings: [
...
+ .define("_WASI_EMULATED_SIGNAL", to: "1", .when(platforms: [.wasi]))
],
linkerSettings: [
...
+ .unsafeFlags(["wasi-emulated-signal"], .when(platforms: [.wasi])),
]
), But then encounter other issue then. (Build and run test fine with normal Linux build) eg.
I guess I should wait for a final release 6.0 of WASM and test it again. |
Still encounter this after I tried the latest 6.0.2 release. This will happen when I try to include the CoreFoundation header. It used to work on 5.x version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm dropping support for Swift 5.10 for all supported platform in my package.
Since WASM does not have a corresponding release yet. I'm switching to the latest 6.0 snapshot
wasm-6.0-SNAPSHOT-2024-09-18-a
toolchain. And I hit with the above error.Is there some extra param I can use to workaround it like #5563 (comment)?
The text was updated successfully, but these errors were encountered: