| Summary: | x11-libs/wxGTK - requires large disk space to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sławek Lis (RETIRED) <slis> |
| Component: | Current packages | Assignee: | Gentoo wxWidgets project <wxwidgets> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | netbox253 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sławek Lis (RETIRED)
2016-07-12 04:23:55 UTC
I'm not a huge fan of CHECKREQS but if you want to want to make a patch I'll add it. I think it may be useful. In my case I've got /var/tmp mounted as tmpfs with some low size limit and I would rather prefer to get an error in early stage than after some time compilling. But it's up to you, it is only suggestion. And also it should force --jobs=1 because actually with jobs >= 1 and tmpfs emerge tries to build two different slots of wxGTK at the same time, and thus it both fails with «no space left of device» errors.
> $ eix wxGTK
> [U] x11-libs/wxGTK
> Available versions:
> (2.8) [M]2.8.12.1-r2
> (3.0) 3.0.3{tbz2} 3.0.4
> (3.0-gtk3) 3.0.3-r300{tbz2} 3.0.4-r300
(it tries to build (3.0) and (3.0-gtk3) slots in the same time)
If you use --jobs and tmpfs, it's your job to ensure things fit... There are some neat portage bashrc hacks around used by some that allow to flag a set of packages as "don't run this in parallel with any of the others". Or just don't use tmpfs for those (per-package PORTAGE_TMPDIR via package.env), or increase it and have a swap to fallback on, or... (In reply to Mart Raudsepp from comment #4) > If you use --jobs and tmpfs, it's your job to ensure things fit... > There are some neat portage bashrc hacks around used by some that allow to > flag a set of packages as "don't run this in parallel with any of the > others". Or just don't use tmpfs for those (per-package PORTAGE_TMPDIR via > package.env), or increase it and have a swap to fallback on, or... Yes. I know all this stuff. Except that I can not guess in advance that this package requires at least 3.5 Gb to build and that it will fail in my current configuration with jobs >= 1. |