the final size of the dir is 5gb on arm as listed by portage in the logs just before merging, but it's propably a bit more than that during lto linking. Reproducible: Always Steps to Reproduce: 1. emerge firefox with USE=lto 2. wait 3. see failure with available tmp space of only a bit more than 4gb Actual Results: build fails due to insufficent disk space Expected Results: should pass I think to add lto to the 8gb list will fix it: pkg_pretend() { # Ensure we have enough disk space to compile if use pgo || lto || use debug || use test ; then CHECKREQS_DISK_BUILD="8G" else CHECKREQS_DISK_BUILD="4G" fi check-reqs_pkg_setup }
since this is defined in the ebuilds now and no longer in the eclasses: this affects firefox and thunderbird, seamonkey not since it hasn't got lto available.
amd64 with lto enabled needs 5.8gb at max
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a051937fb27aa3c29ed6f40ab00a42e8ac21e51c commit a051937fb27aa3c29ed6f40ab00a42e8ac21e51c Author: Jory Pratt <anarchy@gentoo.org> AuthorDate: 2019-09-29 01:32:07 +0000 Commit: Jory Pratt <anarchy@gentoo.org> CommitDate: 2019-09-29 01:32:07 +0000 www-client/firefox: add lto to 8G disk check Closes: https://bugs.gentoo.org/694462 Package-Manager: Portage-2.3.76, Repoman-2.3.17 Signed-off-by: Jory Pratt <anarchy@gentoo.org> www-client/firefox/firefox-68.1.0.ebuild | 2 +- www-client/firefox/firefox-69.0.1.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
