Sam Clegg

The fix for this has not yet landed.

Likely in a week or two. However you can try it today using `emsdk install tot`

> > stated above that requiring users to explicitly pass `-lwasi-emulated-pthread` probably isn't what users expect. > > We could also change the clang compiler driver to do so. I...

> To put forth an idea which I do know will work, but I realize may be controversial: merge "emulated pthreads" directly into wasi-libc. Don't require `-lwasi-emulated-pthread` or `-DWASI_EMULATED_PTHREAD` and...

> Okay, let me try to approach this from the other end. > > 1. Is it desired by wasi-sdk maintainers to be able to build (for example; not exclusively)...

> From my perspective, the desired end result is that the opt-in is done at the build system level (`./configure` or `cmake` option), and doesn't require patching either wasi-sdk or...

Can you trying installing the `-asserts` version of the sdk (e.g. `./emsdk install latest-asserts`) and include the backtrace, and the full failing command line?

I don't see the emcc command line here. Perhaps you could have your compile script echo the commands? Especially the ones that fail? Also, sadly the wasm-ld command here is...

Can you give an example? Are the inputs being passed to gcc and emcc both the same form (e.g. object files and ar archives) or are you using something like...

The only difference that we would expect to see relates to `common` symbols. The llvm WebAssembly backend doesn't support common symbols and defaults to `-fno-common`. Does adding `-fno-common` to your...