-
Notifications
You must be signed in to change notification settings - Fork 477
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
Failing wasip1
build after upgrade to cc-1.0.100
#1109
Comments
cc @antaalt can you help me with this issue please? |
I am curious as to how you were building to WASI without a particular setup, for the fix of the build, you can download WASI sysroot from WASI SDK GitHub release pages and setup the WASI_SYSROOT targeting the folder. You will probably still get issues as there is also an issue that need to be fixed with targets |
Hello @Niederb can you try cc 1.0.102 to see if it fixed your issue? |
Ok I think we'd need to make the |
Just to confirm: cc 1.0.103 fixed the issue for me 👍 |
I have a failing build for
wasip1
after one of my transitive dependencies upgradedcc
tov1.0.100
(See https://github.com/scs/substrate-api-client/actions/runs/9671307108/job/26681692693 for the failing build)
This seems to be caused by this commit: 6a6107a
I'm not quite sure how to fix this. So far we relied on a standard Github runner for our builds and no additional setup for wasi was needed.
The text was updated successfully, but these errors were encountered: