From: Jack <ostroffjh@users.sourceforge.net>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] how to prevent ebuild from checking for available space
Date: Fri, 22 Mar 2024 12:57:34 -0400 [thread overview]
Message-ID: <a3e45c4a-ad8f-4553-b350-30db87de8643@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
In this case, the offending package is dev-lang/rust, but this has
happened to me previously with other packages that require a lot of
space and time to build.
The build fails for any reason. Since it has already progressed over
half way through the build, I would like to continue the build instead
of starting from scratch. I fix whatever caused the issue. In this
particular case, it failed for out of space, so I added another G to the
ramdisk mounted at /var/tmp/portageg. I issue "ebuild
path/to/package.ebuild compile" but it fails immediately because there
isn't enough free space. The problem is that it's checking for enough
free space to do the entire build, not just to continue from where it
left off.
I've done some searching, and found one old forum post which suggests to
just temporarily remove the space check from the ebuild.
In this case, that seems to be line 236 of
/usr/portage/dev-lang/rust/rust-1.75.0-r1.ebuild, which is
"CHECKREQS_DISK_BUILD=${M}M check-reqs_pkg_${EBUILD_PHASE}" the last
line withing pre_build_checks(). However, if I comment out that line,
and run "ebuild path/to/ebuild manifest" another attempt to compile
still gives the same error about not enough space.
Am I commenting the wrong line? Have I missed something about where
this check is atually done? Is it actually possible to do what I'm
trying to do?
Thanks for any pointers or suggestions.
Jack
[-- Attachment #2: Type: text/html, Size: 2006 bytes --]
next reply other threads:[~2024-03-22 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 16:57 Jack [this message]
2024-03-22 20:22 ` [gentoo-user] how to prevent ebuild from checking for available space Neil Bothwick
2024-03-22 20:32 ` Jack
2024-03-23 9:20 ` Neil Bothwick
2024-03-25 11:32 ` Wol
2024-03-23 0:11 ` Jack
2024-03-24 1:04 ` Bryan Gardiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3e45c4a-ad8f-4553-b350-30db87de8643@users.sourceforge.net \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox