gh-100340: Allows -Wno-int-conversion for wasm#100341
Conversation
|
I looked at the output for https://buildbot.python.org/all/#/builders/1046 , but I couldn't find any way to tell what version of the WASI SDK was used to build Python. I know that @tiran set up the buildbots using https://github.com/tiran/ansible-wasm-buildbot . |
@brettcannon The buildbot is using version 16 according to https://github.com/tiran/ansible-wasm-buildbot/blob/main/roles/wasi-sdk/defaults/main.yml#L3 |
64a65f3 to
8fe9902
Compare
|
This worked on |
|
@kushaldas any reason this wasn't backported? |
|
Came here from your recent blog post — as a small build change that can be considered a bug fix, and would give the benefit of keeping various python versions compatible with the latest wasi runtime, this seems fine to backport! |
|
Thanks @kushaldas for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Fixes pythonGH-100340 allows -Wno-int-conversion for wasm (cherry picked from commit 75c8133) Co-authored-by: Kushal Das <mail@kushaldas.in>
|
GH-106066 is a backport of this pull request to the 3.11 branch. |
Adds new configuration directive to disable
int-conversionand then using it for thewasm32-wasibuild only. This allows us to build on the version 17 of the wasm-sdk.How to test manually?
Install the version 17 of the SDK and then run the following command: