| Summary: | dev-python/graph-tool takes ages for build because of -j1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | gentoo |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
graph-tool is a humongous memory hog, and easily goes above 2GB per $CC process. The best option would be to set -j to total_memory / 4GiB, but I'm not aware of a non-terrible way to specify that. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f67a3f792c780157aa926693d3d28f57eb870f9 commit 7f67a3f792c780157aa926693d3d28f57eb870f9 Author: David Seifert <soap@gentoo.org> AuthorDate: 2020-09-27 22:32:19 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2020-09-27 22:32:19 +0000 dev-python/graph-tool: Do not build with -j1 Closes: https://bugs.gentoo.org/744088 Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: David Seifert <soap@gentoo.org> dev-python/graph-tool/graph-tool-2.35.ebuild | 2 +- dev-python/graph-tool/graph-tool-9999.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) |
From ebuild: src_compile() { # most machines don't have enough ram for parallel builds python_foreach_impl run_in_build_dir emake -j1 } Since it doesn't fail because of broken parallel build but instead for missing ram, I'd suggest to workvaround and manage the parallel jobs according to the available ram.