On bazel with sandboxing disabled (or when not available, e.g. Windows), multiple parallel binaries will fail to build due to a shared file being written by the compiler: tmp.tar.
I believe this can be easily solved by changing tmp.tar to a filename that includes the current build rule's name, to make it unique. But I haven't managed to test this.
On bazel with sandboxing disabled (or when not available, e.g. Windows), multiple parallel binaries will fail to build due to a shared file being written by the compiler: tmp.tar.
This filename comes from https://github.com/emscripten-core/emsdk/blob/ce74ca2b1c968f897150bdc55daa9e3c12a3fefc/bazel/emscripten_toolchain/link_wrapper.py#L162
I believe this can be easily solved by changing tmp.tar to a filename that includes the current build rule's name, to make it unique. But I haven't managed to test this.