Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 588640 - x11-libs/wxGTK - requires large disk space to build
Summary: x11-libs/wxGTK - requires large disk space to build
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor with 1 vote (vote)
Assignee: Gentoo wxWidgets Herd
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-12 04:23 UTC by Sławek Lis (RETIRED)
Modified: 2018-08-04 12:24 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sławek Lis (RETIRED) gentoo-dev 2016-07-12 04:23:55 UTC
As it needs more than 3.5G of disk space it may be nice to set CHECKREQS_DISK_BUILD variable.
Comment 1 Ryan Hill (RETIRED) gentoo-dev 2016-07-14 02:44:55 UTC
I'm not a huge fan of CHECKREQS but if you want to want to make a patch I'll add it.
Comment 2 Sławek Lis (RETIRED) gentoo-dev 2016-07-14 05:18:16 UTC
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.
Comment 3 Fab 2018-08-04 09:07:04 UTC
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)
Comment 4 Mart Raudsepp gentoo-dev 2018-08-04 10:58:51 UTC
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...
Comment 5 Fab 2018-08-04 12:24:58 UTC
(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.