[Pkg-chromium-maint] Bug#747135: chromium: FTBFS on i386 due to 32bit linker

James McCoy jamessan at debian.org
Wed May 7 19:26:25 UTC 2014

On Mon, May 05, 2014 at 10:39:17PM +0200, Andreas Cadhalpun wrote:
> chromium still fails to build on i386.
> The tail of the build log is [1]:
> /usr/bin/ld.gold: warning: hidden symbol 'hb_buffer_create' in out/Release/obj.target/third_party/harfbuzz-ng/libharfbuzz-ng.a(out/Release/obj.target/third_party/harfbuzz-ng/../../harfbuzz-ng/third_party/harfbuzz-ng/src/hb-buffer.o)
> is referenced by DSO
> /usr/lib/gcc/i486-linux-gnu/4.8/../../../i386-linux-gnu/libpangoft2-1.0.so
> /usr/bin/ld.gold: fatal error: out/Release/chrome: mmap: failed to allocate
> 2237642984 bytes for output file: Cannot allocate memory
> collect2: error: ld returned 1 exit status
> make[1]: *** [out/Release/chrome] Error 1
> make[1]: Leaving directory `/«PKGBUILDDIR»/src'
> make: *** [debian/stamp-makefile-build] Error 2

For what it's worth, I was able to build* with gcc/g++-4.9 in my x86 VM.
There were memory usage improvements made in 4.9 which might be helping

* The build failed due to running out of disk space instead of running
  out of memory.

I couldn't figure out how to tell debian/rules to use gcc/g++-4.9, when
testing this, so I just added gcc/g++ scripts in $PATH that exec'ed


More information about the Pkg-chromium-maint mailing list