[Pkg-chromium-maint] Bug#765169: closed by Michael Gilbert <mgilbert at debian.org> (Re: Bug#765169: chromium 38.0.2125.101-1 fails to build on i686 with 2 gigs of RAM and 2 gigs of swap)

[Mikko Rapeli]

On Mon, Oct 13, 2014 at 07:33:16PM +0000, Debian Bug Tracking System wrote:
> Date: Mon, 13 Oct 2014 15:29:58 -0400
> From: Michael Gilbert <mgilbert at debian.org>
> To: 765169-close at bugs.debian.org
> Subject: Re: [Pkg-chromium-maint] Bug#765169: chromium 38.0.2125.101-1
>  fails to build on i686 with 2 gigs of RAM and 2 gigs of swap
> 
> On Mon, Oct 13, 2014 at 2:50 PM, Mikko Rapeli wrote:
> > I'm failing to reproduce 38.0.2125.101-1 build on my i386/i686 laptop
> > with 2 gigs of RAM and another 2 gigs of swap.
> 
> The memory exhaustion error is rather expected with that limited
> amount of ram.  You can fiddle around with some of the LDFLAGS in
> debian/rules to possibly achieve some linker memory reduction.

The problem is not about limited amount of ram. It's about limited
amount virtual memory.

> > How was the i386 binary version actually build?
> 
> See below.
> 
> > Is PAE and more than 4 gigs of virtual memory needed?
> 
> Would probably work, haven't tried.

Well I did. PAE did not help. Neither did switch to ld.gold.

> > Is AMD64 CPU and kernel and possibly i386 userspace needed to build the package?
> 
> This is what's done on the buildds.  i386 chroot an amd64 machine.

As a Debian user I'm for the first time now confronted with an
open source package on my architecture which does not compile on that
architecture. It's nice that the binary is provided but IMO it belongs
to contrib or non-free since the same architecture is not able to compile
it.

This propably applies to all 32bit archs but chromium is already limited
to amd64 and i386 for this very reason.

-Mikko