I just emerged icedtea-7, which quit about an hour into the build with an out-of-disk-space error. du showed me that the package had already used 5.5 GB before it quit. I deleted a few things and got about 6.5 GB free and the second try got the package installed. Reproducible: Always The libreoffice already has such a test. Is it practical to cut-paste that test into the icedtea ebuild? Thanks guys.
it could be as well added to an eclass or EAPI=6? maybe a variable in every ebuild: NEED_TMP_SPACE="6G" then we'd need a tool to calculate that value so the ebuild-devs don't need to manually measure it
I fell right into the same pit: https://bugs.gentoo.org/show_bug.cgi?id=452774
*** Bug 452780 has been marked as a duplicate of this bug. ***
Apparent size is 5.8GB, we are indeed at the upper end of what we can expect.
(In reply to comment #1) > it could be as well added to an eclass or EAPI=6? maybe a variable in every > ebuild: NEED_TMP_SPACE="6G" > then we'd need a tool to calculate that value so the ebuild-devs don't need > to manually measure it Seems to be somewhat implemented currently: CHECKREQS_DISK_BUILD="6G" can be found in /usr/portage/app-office/libreoffice/libreoffice-4.0.1.2.ebuild (seems to be the "check-reqs" eutils-class)
Latest icedtea-7.2.4.1 needs nealy 8GB of disk space: 7.7G /var/tmp/portage/dev-java/icedtea-7.2.4.1 Can we please get a proper check in the ebuild?
>+CHECKREQS_DISK_BUILD="9G" >+ >-inherit java-pkg-2 java-vm-2 pax-utils prefix versionator virtualx flag-o-matic >+inherit check-reqs java-pkg-2 java-vm-2 pax-utils prefix versionator virtualx >flag-o-matic >@@ -151,6 +153,12 @@ > S="${WORKDIR}"/${ICEDTEA_PKG} > >+pkg_pretend() { >+ check-reqs_pkg_pretend >+} >+ > pkg_setup() { >+ check-reqs_pkg_setup + 22 Jul 2013; Tom Wijsman <TomWij@gentoo.org> icedtea-7.2.4.1.ebuild, + metadata.xml: + Check for at least 9G of build space, current version is close to 8G without + debug information and LTO.
