Re: gkrust compilation RAM requirements and 32-bit systems

2018-02-26 Thread Henri Sivonen
On Fri, Feb 9, 2018 at 2:05 PM, Henri Sivonen wrote: > On Fri, Feb 9, 2018 at 12:00 PM, Emilio Cobos Álvarez > wrote: >> On 02/09/2018 10:49 AM, Henri Sivonen wrote: >>> Is there some trick to make gkrust compilation succeed on a 32-bit system? >> >> The

Re: gkrust compilation RAM requirements and 32-bit systems

2018-02-09 Thread Henri Sivonen
On Fri, Feb 9, 2018 at 12:00 PM, Emilio Cobos Álvarez wrote: > On 02/09/2018 10:49 AM, Henri Sivonen wrote: >> Is there some trick to make gkrust compilation succeed on a 32-bit system? > > The BSD folks seem to be using --disable-debug-symbols for that, see >

Re: gkrust compilation RAM requirements and 32-bit systems

2018-02-09 Thread Ted Mielczarek
On Fri, Feb 9, 2018, at 4:49 AM, Henri Sivonen wrote: > Is it expected that Firefox can no longer be built on a 32-bit system? Yes. > 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

Re: gkrust compilation RAM requirements and 32-bit systems

2018-02-09 Thread Emilio Cobos Álvarez
On 02/09/2018 10:49 AM, Henri Sivonen wrote: > Is there some trick to make gkrust compilation succeed on a 32-bit system? The BSD folks seem to be using --disable-debug-symbols for that, see https://bugzilla.mozilla.org/show_bug.cgi?id=1401093 -- Emilio

gkrust compilation RAM requirements and 32-bit systems

2018-02-09 Thread Henri Sivonen
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