Skip to content
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

Fix carton sdk install on linux(aarch64) #386

Merged
merged 1 commit into from
Oct 16, 2022

Conversation

gibachan
Copy link
Contributor

On linux for aarch64 architecture, carton sdk install command fails with the following error.

# carton sdk install wasm-5.7.1-RELEASE
- checking Swift compiler path: /root/.carton/sdk/wasm-5.7.1-RELEASE/usr/bin/swift
- checking Swift compiler path: /root/.swiftenv/versions/wasm-5.7.1-RELEASE/usr/bin/swift
Fetching release assets from https://api.github.com/repos/swiftwasm/swift/releases/tags/swift-wasm-5.7.1-RELEASE
Response contained body, parsing it now...
Response succesfully parsed, choosing from this number of assets: 6
The Swift version wasm-5.7.1-RELEASE was not found
Error: Invalid version wasm-5.7.1-RELEASE

The reason seemed to be a wrong download URL for that.

( carton sdk install searches the download URL from https://api.github.com/repos/swiftwasm/swift/releases/tags/swift-wasm-5.7.1-RELEASE )

@kateinoigakukun kateinoigakukun added the bug Something isn't working label Oct 16, 2022
Copy link
Member

@kateinoigakukun kateinoigakukun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch! Thanks 😸

@kateinoigakukun kateinoigakukun enabled auto-merge (squash) October 16, 2022 13:30
@kateinoigakukun kateinoigakukun merged commit 74b8ca6 into swiftwasm:main Oct 16, 2022
@gibachan gibachan deleted the linux_aarch64_install_path branch October 16, 2022 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants