-
Notifications
You must be signed in to change notification settings - Fork 189
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
Using wasi-sdk-20 pre-release on Ubuntu 20.04 #303
Comments
@yamt had mentioned this in a comment previously, but I personally was not too interested in maintaining compatibility with a bunch of old glibc versions ("how far to go back?" "would this cause friction with future integration?" etc.). IIUC, this boils down to using Ubuntu's 20.04 image during compilation instead of 22.04; I don't understand what restrictions are preventing other projects from also using 22.04? Is this request of wasi-sdk just a symptom of another issue somewhere else? That being said, I'm actually not opposed to supporting some older versions of glibc, though; I would gladly review PRs along these lines if we figure out a limit to the versions supported and it meshes with the work I did to script the release process in #295. |
as far as i know, no one is asking "compatibility with a bunch of old glibc versions". |
Exclude dist-ubuntu-latest to prefer dist-ubuntu-bionic, which is compatible with wider distributions. cf. WebAssembly#273 (comment) WebAssembly#303
Exclude dist-ubuntu-latest to prefer dist-ubuntu-bionic, which is compatible with wider distributions. cf. #273 (comment) #303
Ok, now that #307 is merged should we close this? I will use the older versions in the |
i want it "soon". i have no idea when |
@eloparco, can you try out the |
Thanks! I tried it and it seems to work: bytecodealliance/wasm-micro-runtime#2095 |
Hello,
In a GitHub action job on Ubuntu 20.04, I'm trying to use the wasi-sdk-20 pre-release, but I'm getting the following eror:
Is there any planned fix to support older versions of glibc?
Thanks
The text was updated successfully, but these errors were encountered: