Bug#747135: chromium: FTBFS on i386 due to 32bit linker
Hi! I just tested this by adding gcc (= 4:4.9.0-2exp2), g++ (= 4:4.9.0-2exp2), to the build-deps and rebuilding inside cowbuilder. With gcc-4.9 chromium is finally able to be linked: LINK(target) out/Release/chrome: Finished touch out/Release/obj.target/chrome/chrome.stamp make[1]: Leaving directory '/tmp/buildd/chromium-browser-34.0.1847.137/src' touch debian/stamp-makefile-build Grüße, Sven. signature.asc Description: OpenPGP digital signature
Bug#747135: chromium: FTBFS on i386 due to 32bit linker
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 here. * 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 gcc/g++-4.9. James -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747135: chromium: FTBFS on i386 due to 32bit linker
Package: chromium Version: 34.0.1847.132-1 Severity: grave Justification: FTBFS on i386 blocks #746034 Control: block 746034 by -1 Dear maintainer, 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 This has already been pointed out by Sven Hartge in bug #745794 [2]: It seems the linker, being a 32bit application, trips over the 3GB memory limit for 32bit applications. It would be great, if you found a way to fix this, because the chromium version in jessie is currently uninstallable (#746034), so on i386 there is currently no installable chromium in jessie/sid. Best regards, Andreas 1: https://buildd.debian.org/status/package.php?p=chromium-browser 2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745794#13 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
