-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Build fails with WASI SDK 21 #113516
Comments
What version of the WASI-SDK did you use? |
Hi - I believe I was failing with wasi-sdk-20.
It builds fine for wasi-sdk 16.
From: Brett Cannon ***@***.***>
Sent: Wednesday, January 3, 2024 6:05 PM
To: python/cpython ***@***.***>
Cc: Romanczyk, Piotr ***@***.***>; Author ***@***.***>
Subject: [External] Re: [python/cpython] wasi build appears to fail (Issue #113516)
What version of the WASI-SDK did you use?
-
Reply to this email directly, view it on GitHub<#113516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBG4R5W4VEQWQCU6ZJIGMDYMXP2NAVCNFSM6AAAAABBEQFICCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGA4DSMZQGA>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
**** Resideo WARNING: This email was sent from outside of Resideo and the sender cannot be verified. Use CAUTION before opening file attachments, links, or replying to the email. For additional information please contact the Resideo Service Desk ****
|
It builds fine for me under WASI-SDK 20. Can you share all 4 commands you used w/ |
Sorry for the delay...
I've used exact same commands as listed on ./Tools/wasm README.md for WASI builds:
python Tools/wasm/wasi.py configure-build-python
python Tools/wasm/wasi.py make-build-python
python Tools/wasm/wasi.py configure-host
python Tools/wasm/wasi.py make-host
I am a bit confused about the wasi-sdk versions - when I get wasi-sdk-16 tagged source I get this:
./wasi-ld -version
LLD 14.0.4
The above version builds just fine from cpython main
I thought it was v 20 failing and I can't tell exactly which wasi-sdk version is the one failing in my setup
but the one that fails has this version of lld installed:
./wasi-ld -version
LLD 17.0.6
Hope that helps
From: Brett Cannon ***@***.***>
Sent: Thursday, January 4, 2024 1:29 PM
To: python/cpython ***@***.***>
Cc: Romanczyk, Piotr ***@***.***>; Author ***@***.***>
Subject: [External] Re: [python/cpython] wasi build appears to fail (Issue #113516)
It builds fine for me under WASI-SDK 20.
Can you share all 4 commands you used w/ wasi.py? Do you get a different result if you use wasi.py build?
-
Reply to this email directly, view it on GitHub<#113516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBG4R5S7YJEPGJKURS22FDYM3YE7AVCNFSM6AAAAABBEQFICCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGU3DSNZSGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
**** Resideo WARNING: This email was sent from outside of Resideo and the sender cannot be verified. Use CAUTION before opening file attachments, links, or replying to the email. For additional information please contact the Resideo Service Desk ****
|
Unfortunately w/o knowing what WASI-SDK version is having issues I don't know how to help since I don't have these failures under WASI-SDK 20. If it's WASI-SDK 21 (which we have not tried to support yet), then that might be the cause, but then that means they may have broken something. |
I opened WebAssembly/wasi-sdk#372 to see if there's an easy way to find this out. |
Understood - no problem.
I've got it to build and working with wasi-sdk-16.0 - I will try wasi-sdk-20.0 later this week.
Thanks!
From: Brett Cannon ***@***.***>
Sent: Monday, January 8, 2024 2:54 PM
To: python/cpython ***@***.***>
Cc: Romanczyk, Piotr ***@***.***>; Author ***@***.***>
Subject: [External] Re: [python/cpython] wasi build appears to fail (Issue #113516)
Unfortunately w/o knowing what WASI-SDK version is having issues I don't know how to help since I don't have these failures under WASI-SDK 20. If it's WASI-SDK 21 (which we have not tried to support yet), then that might be the cause, but then that means they may have broken something.
-
Reply to this email directly, view it on GitHub<#113516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBG4R53OOAI34QHAPIP6Y3YNRFEPAVCNFSM6AAAAABBEQFICCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRG4ZDQNJSGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
**** Resideo WARNING: This email was sent from outside of Resideo and the sender cannot be verified. Use CAUTION before opening file attachments, links, or replying to the email. For additional information please contact the Resideo Service Desk ****
|
Sounds good! Thanks.
From: Brett Cannon ***@***.***>
Sent: Monday, January 8, 2024 2:57 PM
To: python/cpython ***@***.***>
Cc: Romanczyk, Piotr ***@***.***>; Author ***@***.***>
Subject: [External] Re: [python/cpython] wasi build appears to fail (Issue #113516)
I opened WebAssembly/wasi-sdk#372<WebAssembly/wasi-sdk#372> to see if there's an easy way to find this out.
-
Reply to this email directly, view it on GitHub<#113516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBG4R6E32SP5HZO6PA75U3YNRFPXAVCNFSM6AAAAABBEQFICCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRG4ZTEMRYGY>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
**** Resideo WARNING: This email was sent from outside of Resideo and the sender cannot be verified. Use CAUTION before opening file attachments, links, or replying to the email. For additional information please contact the Resideo Service Desk ****
|
I will close the issue. If you have more information, please comment here or file a new one. |
Fails to build using
|
Filed WebAssembly/wasi-sdk#385 asking for help/input. |
There may have been a change in clang 17 (which WASI SDK 21 uses) where |
OK, I think I have figured it out. 😮💨 If you look at the failure it corresponds to trying to build Line 7458 in 3e7b7df
So now we know why this problem is only showing up for WASI SDK 21, but why the call to Lines 2238 to 2240 in 3e7b7df
If you look at the generated
So it seems Line 3317 in 4684301
And why does this matter? Line 168 in 4684301
And there's the Line 58 in 4684301
Dropping that environment variable gets compiling to work! I will get a PR pulled together for this. But then |
FYI the fix for |
…ythonGH-115495) (pythonGH-115496) (cherry picked from commit 0e4f73b) Co-authored-by: Brett Cannon <[email protected]>
The fixes to get the builds to work are now in, so getting |
Awesome! Great investigation!
I am looking forward to test that build.
…________________________________
From: Brett Cannon ***@***.***>
Sent: Wednesday, February 14, 2024 8:35:45 PM
To: python/cpython ***@***.***>
Cc: Romanczyk, Piotr ***@***.***>; Author ***@***.***>
Subject: [External] Re: [python/cpython] Build fails with WASI SDK 21 (Issue #113516)
The fixes to get the builds to work are now in, so getting test_importlib to pass is next.
—
Reply to this email directly, view it on GitHub<#113516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBG4R7T4EED26VWVYWJ26LYTVQ7DAVCNFSM6AAAAABBEQFICCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVGIZDKNJXGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
**** Resideo WARNING: This email was sent from outside of Resideo and the sender cannot be verified. Use CAUTION before opening file attachments, links, or replying to the email.****
|
I opened #115979 to track the |
Bug report
Bug description:
Hello!
when executing
python3 Tools/wasm/wasi.py make-host
on
ubuntu 22.04
with wasi-ld version: LLD 17.0.6 (tried earlier versions too)Errors are as follows:
if "-Wl" flag removed then clang compiler fails.
CPython versions tested on:
3.13
Operating systems tested on:
Linux
Linked PRs
LDSHARED
when building for WASI #115495LDSHARED
when building for WASI (GH-115495) #115496LDSHARED
when building for WASI (GH-115495) (GH-115496) #115497The text was updated successfully, but these errors were encountered: