The size requirement for rust has been changed to 10 Gb in version 1.41. It seems to be exagerated. I was able to compile it with only 8.3 Gb remaning. Reproducible: Always
Hi, yes, it's on my to-do list. Will add soon. 10G is the maximum I've seen with all the flags enabled, but we can control it a bit depending on useflag. the base requirement is about 6g with no -g* flags and goes up if you add more features.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef89cb77bf9fc16eec9e140e29138adb8d74258a commit ef89cb77bf9fc16eec9e140e29138adb8d74258a Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2020-08-04 23:39:45 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2020-08-04 23:43:11 +0000 dev-lang/rust: improve pre-build checks in 1.45.2 Bug: https://bugs.gentoo.org/709362 Bug: https://bugs.gentoo.org/706292 Package-Manager: Portage-3.0.1, Repoman-2.3.23 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> dev-lang/rust/rust-1.45.2.ebuild | 34 +++++++++++++++++++++++++++++++--- 1 file changed, 31 insertions(+), 3 deletions(-)
While you're messing with the space estimates: How hard would it be to exclude any pre-existing files in /var/tmp/portage/dev-lang/rust* ? I was trying to resume a compile today (ran out of disk space due to me moving things to the root partition while the compile was going). I did what I always do for partially finished long running compiles and used: # ebuild /var/dv/repos/gentoo/dev-lang/rust/rust-1.47.0-r2.ebuild merge The ebuild refused to start due to build requirements not being met (not enough space), but ~11Gb of the used space was the existing partially compiled rust and sources! I hacked the ebuild and ignored the resulting digest warning and it carried on compiling just fine, but I imagine that's more trouble than some would be willing/able to go to. Would the ebuild be able to exclude the files in /var/tmp/portage/dev-lang/rust* so this is avoided?
don't think so, function is complex enough already. you can always do I_KNOW_WHAT_I_AM_DOING=1 emerge dev-lang/rust --oneshot exporting this variable will make the space check a no-op and will go on even if there's not enough space, without editing ebuilds.
just FTR, rust-1.51 failed to compile with 15.5 GiB of free space, despite passing the free space check ... I guess it needs some updating (~arm64, if that matters)
(In reply to kavol from comment #5) > just FTR, rust-1.51 failed to compile with 15.5 GiB of free space, despite > passing the free space check ... I guess it needs some updating (~arm64, if > that matters) can you share the useflags you set for that build?
latest space requirements discussion is in https://bugs.gentoo.org/783768 closing this one
