Previously, the RAM-critical operation during Firefox build was linking libxul, which on Linux was known not to work with 1 GB of RAM but did work with 2 GB of RAM.
Now, when trying to build Firefox (opt build) on ARMv7 Linux with 2.3 GB of *free* RAM at the start of the build, building gkrust fails. (Nightly rustc OOMs and stable rustc causes the system to reboot.) Do I understand correctly that even on an ARMv7 system that has more than 2 GB of physical RAM, a userspace process (rustc) can address only 2 GB and, therefore, with 2.4 GB free at the start of the build and build failing with -j 1, rustc got the maximal RAM it can possibly get? (The reboot bit suggest something other than mere userland virtual address space exhaustion, though. This is with a Chrome OS kernel that doesn't let me enable swap.) Is it expected that Firefox can no longer be built on a 32-bit system? Is there some trick to make gkrust compilation succeed on a 32-bit system? The cross-compilation documentation on MDN seems to predate Rust code in Firefox. Is there an up-to-date guide for compiling Firefox for ARMv7+NEON (or aarch64 for that matter) GNU/Linux on an x86_64 GNU/Linux host? -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
