Summary: | www-client/chromium-21.0.1180.89 compile failed: nacl_bootstrap_raw Error 252 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc <mwlpfz> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
chromium-21.0.1180.89-build.log
build.log |
Description
Marc
2012-09-22 18:23:57 UTC
Created attachment 324648 [details]
chromium-21.0.1180.89-build.log
tail -n200 /var/tmp/portage/www-client/chromium-21.0.1180.89/temp/build.log
Are you possibly hitting bug #394683 ? Please look at the debugging hints in that bug and apply them on your system, then post the results. Are you using any chroots, moving binaries between different systems, or anything non-obvious that might be relevant here? Also, please attach the full build log for reference (compress it). (In reply to comment #2) > Are you possibly hitting bug #394683 ? > > Please look at the debugging hints in that bug and apply them on your > system, then post the results. > > Are you using any chroots, moving binaries between different systems, or > anything non-obvious that might be relevant here? > > Also, please attach the full build log for reference (compress it). /var/tmp/portage is a tmpfs but diskspace seems not to be problem which I already increased from 2 to 8Gb just to make sure. I'm trying with MAKEOPTS="-j1" first as stated in another report (which takes ages) and if this doesnt work I'll apply the debug options. Created attachment 324688 [details]
build.log
I found the problem during rebuilding glibc and it was related to #394683. I copied the files /etc/portage from a different system and had a glibc and binutils config I didnt consider until now. env/sys-devel/binutils CFLAGS="-march=atom -O2 -pipe" CXXFLAGS="${CFLAGS}" Sorry for your time and effort. *** This bug has been marked as a duplicate of bug 394683 *** |