From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about compilation
Date: Sun, 09 Feb 2025 17:06:42 +0000 [thread overview]
Message-ID: <3861831.kQq0lBPeGt@rogueboard> (raw)
In-Reply-To: <CAHVEG0BWYxMyA10wQC5_RBF9=L+MA1sND7jT012uC2xEdUsiag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
On Sunday 9 February 2025 16:44:55 Greenwich Mean Time Jacques Montier wrote:
> Le dim. 9 févr. 2025 à 15:36, Håkon Alstadheim <hakon@alstadheim.priv.no> a
>
> écrit :
> > 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.
>
> Thank you all for your feedback and advice.
> For testing,
> - emerge media-libs/opencv-4.10.0
> - some time later CTRL+C to stop compilation
>
> Then I followed Jack's advice
> - ebuild /var/db/repos/gentoo/media-libs/opencv/opencv-4.10.0.ebuild compile
> - ebuild /var/db/repos/gentoo/media-libs/opencv/opencv-4.10.0.ebuild
> install - ebuild
> /var/db/repos/gentoo/media-libs/opencv/opencv-4.10.0.ebuild qmerge
>
> Everything worked fine, thanks a lot.
>
> Good evening to all,
>
> Best regards,
>
> --
> Jacques
Unless you have a good reason to run each emerge stage separately, you can
just use 'merge' for all of them - you can check 'man ebuild' for an
explanation.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-09 17:07 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
2025-02-09 16:44 ` Jacques Montier
2025-02-09 17:06 ` Michael [this message]
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=3861831.kQq0lBPeGt@rogueboard \
--to=confabulate@kintzios.com \
--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