Thank you for your proposal; it makes sense to me. I have a bit concerns about the number of changes we need to backport, but it should still be worth doing. Would you mind creating backport PRs to each release branch and running ruby.w...katei (Yuta Saito)
We will need more Asyncify space for the upcoming namespace changes as it will introduce more local variables and conditional jumps in asyncify'd functions.katei (Yuta Saito)
Previously, the script was caching any file already present in the destination directory, regardless of its origin. This caused issues when the directory contained files copied from external sources like `autoreconf --install`. For exam...katei (Yuta Saito)
wasi-libc 22 and later support realpath(3) (https://github.com/WebAssembly/wasi-libc/pull/463) but the underlying host syscall may return ENOTSUP. This is typically the case when using incomplete WASI polyfills on web browsers. For such ...katei (Yuta Saito)
This reverts the following commits as it's causing OOM in some cases in ruby/ruby.wasm test suite. * 372515f33c908b36b3f5fbd2edcb34c69b418500 * 3a730be8b464454878a42132f6fecb98ab4c1b5bkatei (Yuta Saito)
we had been using a stub weak definition of `mprotect` in wasm/missing.c so far, but wasi-sdk 23 added mprotect emulation to wasi-libc[^1], so the emulation is now linked instead. However, the emulation doesn't support PROT_NONE and fail...katei (Yuta Saito)
Previously, the script was caching any file already present in the destination directory, regardless of its origin. This caused issues when the directory contained files copied from external sources like `autoreconf --install`. For exam...katei (Yuta Saito)
At first, it’s rare to have a situation where Ruby itself can be built but no C++ compiler is available. The macOS example mentioned in the ticket is an unusual case caused by broken Command Line Tools. Having said that, I agree that ...katei (Yuta Saito)