From: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about compilation
Date: Sun, 9 Feb 2025 15:36:14 +0100 [thread overview]
Message-ID: <a5bcda8a-3266-4532-a0d9-bfbd6ea62f03@alstadheim.priv.no> (raw)
In-Reply-To: <CAHVEG0B76sAaYYTK7KLoaZZvXrX8of3aW0_4KsHYuHKQrVF+hg@mail.gmail.com>
Den 08.02.2025 15:47, skrev Jacques Montier:
> Hello everyone,
>
> Is it possible to stop a compilation midway in the case of a very long
> compilation and then resume it from the same point without having to
> start over from the beginning ?
>
> Thank you for your response.
>
For the big compiles I set PORTAGE_TMPDIR=/pt/ , which I have created
and which is NOT a tmpfs, so it will survive a reboot (and I don't have
enough ram anyway) . You might also want to check FEATURES, either
globally or on a per-package basis, make sure you don't have fail-clean.
Watch out so your newly permanent tmpdir does not fill up.
Then, if it dies for some reason, I do for example:
<code> ebuild `equery w www-client/firefox ` merge. </code>
make or cmake or whatever will do the best it can to pick up where it
left off.
P.S: Search the web to find out to set FEATURES and PORTAGE_TMPDIR in
the environment on a per-package basis, or just prepend the settings to
your command-line.
next prev parent reply other threads:[~2025-02-09 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 14:47 [gentoo-user] Question about compilation Jacques Montier
2025-02-08 19:00 ` Filip Kobierski
2025-02-08 23:07 ` Jack
2025-02-09 0:11 ` Michael
2025-02-09 0:20 ` Dale
2025-02-09 0:23 ` Matt Jolly
2025-02-09 5:28 ` Dale
2025-02-16 17:22 ` Wols Lists
2025-02-16 19:12 ` Dale
2025-02-09 0:46 ` [gentoo-user] " Nuno Silva
2025-02-09 10:23 ` [gentoo-user] " MLR
2025-02-09 14:36 ` Håkon Alstadheim [this message]
2025-02-09 16:44 ` Jacques Montier
2025-02-09 17:06 ` Michael
2025-02-09 17:22 ` Jacques Montier
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=a5bcda8a-3266-4532-a0d9-bfbd6ea62f03@alstadheim.priv.no \
--to=hakon@alstadheim.priv.no \
--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