Changes between Version 159 and Version 160 of firefox


Ignore:
Timestamp:
06/05/2023 10:06:32 PM (13 months ago)
Author:
ken@…
Comment:

Update details re wasm sandboxing

Legend:

Unmodified
Added
Removed
Modified
  • firefox

    v159 v160  
    9595= Sandboxing ==
    9696
    97 From firefox-95 on, the build system wants to use "wasi-sysroot" to sandbox  some of the shipped libraries (by converting to wasm and then back to sandboxed C). That will require, amongst other things, llvm built for WebAssembly (that is default, but BLFS does not enable it), wasi-libc [https://github.com/WebAssembly/wasi-libc], some other supporting packages, and using clang instead of gcc. If you want to do that, look at what Arch is doing.
     97From firefox-95 on, the build system wants to use "wasi-sysroot" to sandbox  some of the shipped libraries (by converting to wasm and then back to sandboxed C). That will require, amongst other things, llvm built for WebAssembly (that is default, but BLFS does not enable it), wasi-libc [https://github.com/WebAssembly/wasi-libc], some other supporting packages, and using clang (we already do that) and probably lld (the llvm linker). If you want to do that, look at what Arch is doing.Please note that it looks as if **static libz.a** is needed to do that, and LFS deletes that.
    9898
    9999For the moment, g++ can be used if you pass --without-wasm-sandboxed-libraries but the changes in gcc-12 mean that the book has moved to using clang++, still without wasm.