public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about compilation
Date: Sat, 08 Feb 2025 18:07:38 -0500	[thread overview]
Message-ID: <HC37OQGA.77DBFBL3.DJEUKVBS@7NIQ6KAE.GOEXPA4Y.QPE2CHZB> (raw)
In-Reply-To: <nVFBByFMm1LOpyXr5J_3fxoDf1iGzj4N-HpBWnEk5-o4MsTgABLq2Mp2u7F9GNJ4VygNU8pD5fnzhCYTNmmBFZ1mlwwxQo4c0zvE4CplUeU=@protonmail.com>

On 2025.02.08 14:00, Filip Kobierski wrote:
> Hi Jacques,
> 
> I think you are looking for SIGSTP or SIGSTOP but I think that's
> not exactly it. From what I know you cannot do that for emerge
> easily. For similar results you might want to set up ccache.
> https://wiki.gentoo.org/wiki/Ccache
> 
> Regards
> Filip
> 
> On Saturday, February 8th, 2025 at 15:47, Jacques Montier  
> <jmontier@gmail.com> wrote:
> 
> > 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.
> > Best regards,
> >
> > --
> > Jacques Montier.
> 
If you really mean just interrupting a compile, then you should be able  
to stop with Ctl-C, and then start/continue by running make or ninja  
again, assuming that is what is used for whatever you are compiling.   
Ccache can help since most of the results of the previous compile  
attempt will have been cached, and so will be completed more quickly  
the next time, but it's not the same as continuing from where it was  
interrupted.

If, as Filip implies, you are asking about interrupting emerge, it's  
easy enough to interrupt, but essentially impossible to continue from  
where it left off.  "emerge --continue" will just try to emerge every  
package from the interrupted emerge which was not completed, but it  
will start each one from scratch.  What has often, but not alwasy  
worked for me, is to use ebuild directly.  "ebuild  
.../path/to/package.ebuild compile" will figure out that everything  
prior to the compile was completed, and then issue the make or ninja  
commands, which will just pick up where they left off.  If that does  
work, then you need to repeat the ebuild, but with the install and then  
the qmerge commands.  The only problem with that (for me, at least) is  
that ebuild does not leave exactly the same lines in emerge.log, so a  
package installed that way will not show up in "gentlop -t package"  
output.



  reply	other threads:[~2025-02-08 23:08 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 [this message]
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
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=HC37OQGA.77DBFBL3.DJEUKVBS@7NIQ6KAE.GOEXPA4Y.QPE2CHZB \
    --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