Summary: | www-client/firefox-13 fails during linking | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrizio Bassi <patrizio.bassi> |
Component: | New packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrizio Bassi
2012-06-09 11:03:45 UTC
> malloc() ../../sandbox-2.5/libsandbox/libsandbox.c:resolve_path():263: malloc(8192) failed: Cannot allocate memory
It appears that you are running out of memory. pgo needs around 3 GB during final link stage. Can you try again with pgo disabled?
actually i have 4gb installed ram and i've always used pgo (even 12.0) (In reply to comment #2) > actually i have 4gb installed ram and i've always used pgo (even 12.0) Close everything and test again, really pgo useflag is fixing to be p.masked, it is causing more headache then it is worth. Please do not mask USE="pgo", I have been using it since firefox-9 or -10 and never had problems with it. Suggestion: Raising the warning threshold (currently 512MB) and advising people to not have ${PORTAGE_TMPDIR} on tmpfs. (In reply to comment #4) > Please do not mask USE="pgo", I have been using it since firefox-9 or -10 > and never had problems with it. > > Suggestion: Raising the warning threshold (currently 512MB) and advising > people to not have ${PORTAGE_TMPDIR} on tmpfs. PORTAGE_TMPDIR has nothing to do with anything, it already has a check for 8G of space before the compile even begins for pgo builds and 4G for non pgo builds, while this is not a fatal check the warning should be more then enough. There are too many variables that come into play when dealing with mozilla products and space needed and memory needed to ensure a successful compile every time i enabled swap and it worked second time. i'm going to close this, sorry for bugspam |