As previously discussed in #174, this is due to WebAssembly/wasi-libc#617, which was fixed in WASI-SDK 28. However, WASI-SDK 28 also broke the wasm32-wasip2 target in various ways, e.g. WebAssembly/wasi-libc#640, so we'll need to wait for WASI-SDK 29 at least before we can pull that fix in (or backport the fix if we get desperate).
As previously discussed in #174, this is due to WebAssembly/wasi-libc#617, which was fixed in WASI-SDK 28. However, WASI-SDK 28 also broke the
wasm32-wasip2target in various ways, e.g. WebAssembly/wasi-libc#640, so we'll need to wait for WASI-SDK 29 at least before we can pull that fix in (or backport the fix if we get desperate).