Summary: | www-client/chromium ebuild should check RAM+swap size | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sasha Polonsky <apl> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | bircoph |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sasha Polonsky
2012-06-06 11:43:25 UTC
*** This bug has been marked as a duplicate of bug 319929 *** This bug is not a duplicate of 319929 . The bug 319929 is about disk space, but this bug is about RAM and swap space. Unlike but 319929 , it is not fixed yet. The memory requirements to build a package depend on the compiler, linker, CFLAGS and LDFLAGS. They can vary dramatically, so it is infeasible to impose a memory requirement check in ebuilds. If so, why libreoffice ebuild checks for at least 512M of RAM ? Also, please tell me the combination of USE flags I should emerge chromium with so linker is not killed on a machine with 512M of RAM and 500M of swap. We have the same problem here: on hosts with 2.0-2.5 GB of RAM and a lot of swap it is quite possible to build chromium (e.g. during night). The only solution I found is to export I_KNOW_WHAT_I_AM_DOING="yes" emerge chromium But this solution can be found only by reading check-reqs.eclass and is not documented anywhere, thus users can't access it easily. Moreover as I can see, check-reqs.eclass does not provide a way to check for ram+swap space, thus this functionality should be added there and then used in the chromium ebuilds. Probably adding some flag CHECKREQS_CONSIDER_SWAP and documenting it (at least printing a hint on memory check failure) will be a good deal. |