Bug 1649631 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I'm attempting to stand up some builds with clang trunk, currently version 11.

In version 11, the clang tree has a [breaking change to wasm](https://github.com/WebAssembly/wasi-libc/commit/d9066a87c04748e7381695eaf01cc5c9a9c3003b) which requires that we pick up the [corresponding change in wasi-libc](https://github.com/WebAssembly/wasi-libc/commit/d9066a87c04748e7381695eaf01cc5c9a9c3003b) which is available in [wasi-sdk release 10](https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-10).

However, when I update the rev for the wasi-sysroot task, the builds fail with:
```
 LucetcError { inner: ErrorMessage { msg: "Unknown module for symbol `wasi_snapshot_preview1::proc_exit`" }
```
From this point, I'm not super familiar, so this is just a guess, but: I notice that this symbol appeared in a recent [change to the bytecodealliance/lucet repo](https://github.com/bytecodealliance/lucet/commit/81e1b97e5046c12f450046cc8452c70c8793d229). Does the PLSysSec fork need to pick it up?
I'm attempting to stand up some builds with clang trunk, currently version 11.

In version 11, the clang tree has a [breaking change to wasm](https://github.com/llvm/llvm-project/commit/00072c08c75050ae2c835b7bb0e505475dbcd7b9) which requires that we pick up the [corresponding change in wasi-libc](https://github.com/WebAssembly/wasi-libc/commit/d9066a87c04748e7381695eaf01cc5c9a9c3003b) which is available in [wasi-sdk release 10](https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-10).

However, when I update the rev for the wasi-sysroot task, the builds fail with:
```
 LucetcError { inner: ErrorMessage { msg: "Unknown module for symbol `wasi_snapshot_preview1::proc_exit`" }
```
From this point, I'm not super familiar, so this is just a guess, but: I notice that this symbol appeared in a recent [change to the bytecodealliance/lucet repo](https://github.com/bytecodealliance/lucet/commit/81e1b97e5046c12f450046cc8452c70c8793d229). Does the PLSysSec fork need to pick it up?

Back to Bug 1649631 Comment 0