The reporter of bug #745794[1] suggested that it's enough to add the
proper build-dependency on libkrb5-dev. Is this correct, or are there
other problems that make finding a fix difficult?
(FYI: I am no DD, just a normal user.)
I tried to rebuild chromium in a pristine Sid chroot with pbuilder,
resulting in this error from ld:
/usr/bin/ld.gold: fatal error: out/Release/chrome: mmap: failed to allocate
2237530592 bytes for output file: Cannot allocate memory
The system I am compiling chromium on has 32GB of physical memory and 16GB
of swap space, none of which were full in any way.
It seems the linker, being a 32bit application, trips over the 3GB memory
limit for 32bit applications.
This kind of error can be found quite regular in the bug tracker for
chromium, the advise was always something like man, gotta use a 64bit
linker, dude!
I wonder how one should do this in a buildd environment.
Grüße,
Sven.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
