From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 934AA1582EF for ; Sun, 09 Feb 2025 00:22:00 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 811033430CE for ; Sun, 09 Feb 2025 00:22:00 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 6970E11047E; Sun, 09 Feb 2025 00:20:55 +0000 (UTC) Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id 57EE91103CB for ; Sun, 09 Feb 2025 00:20:54 +0000 (UTC) Received: by mail-il1-x12e.google.com with SMTP id e9e14a558f8ab-3ce886a2d5bso32480955ab.1 for ; Sat, 08 Feb 2025 16:20:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739060453; x=1739665253; darn=lists.gentoo.org; h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from :references:to:subject:from:to:cc:subject:date:message-id:reply-to; bh=BOBRR9bVGnoAYJTiRpMXdzTMvWD/sjozQQAopOHR4r4=; b=Oc2xR+TRHtlI+bo+kE0vhL4JU9HfxGwbITLDfvVtFTutH6JNFVUldBbdVGv7vJLVqx xkVr/VJ79Go9wnDTzV5iUMLUolo7UZpvgNM6A5LLfVfEGmtcYlgRoyRdfQa0mDmvq28J 6gTm8q5a+wl689DptKDL9ptnfhLDM+M2BVJ0DSlsJZ9Hcq+HsST+n3bY0yWQ53Mw3t8A cT966BPgKVzk2wOI8okgzmUuXcNxAsan+mr3x3XRy1sLVYEaAH0PbJPEDGHRpkz+ilId eQ/d29Xidz/oMtRz3/4IOWktDRCepdo5b7eEGnDgAzCi6nbeTUAibJh8kPFO35hXRxPJ zGSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739060453; x=1739665253; h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from :references:to:subject:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=BOBRR9bVGnoAYJTiRpMXdzTMvWD/sjozQQAopOHR4r4=; b=SoHJ9CNxIxZVDj5AYvjy+Ma6sDqW+Cp7izwf1TlzrmHQUsEyrbPlIt3Q3Bvbh/SFWI FW/8KhRcDxcqaxZIO+hbW8SMrSdeX868xS5MxRlznWw96lmRV+8oBJtpgBSeW72b0vpj 6tHcPZLqhFYQcuDt3OvPSqg33AFs3RbBWJY95Dzqz9PUfiVD6iSr3yCj1ZeYLHLaiEZ3 v4tRuUuU1t9dE6a6kptUUob2Uw5AOr7aFDCUsvKJiSHMwDlMbBGVWS30RUo/iIEcmOU0 fTz4EnaP/WIZz5++Pp+XQpb+6CBMr71qlqpjz8t4j5dQaav/jBdDwdsjhQfXWGGNZizC vQnQ== X-Gm-Message-State: AOJu0YxBP2UDnrDue57wppTkomLxIWBAAS3s16rcPCzUHXLdgb3ilSi1 JxtrgaLuE3bQj+Dat3tSQab2fpVMAQJcQoh3jjarMQMnw3tLhKVJ X-Gm-Gg: ASbGnct4JBBKE2ShEJh7Smu3AnM5dMewGz2Xc4Q41J/vAlaF3cTxYAZggpdafVcn2yg FAigSBXIZ7ONpQ3i0z0LVF0QPL+Pn6De07rWyCYl9GndL/pZPxK4nwG8PAQc9Dxqy1aYOpMbdhD a5mBWNWVVnOT3Ms+wZiVBIH62lf6e+Z/HTe8jJUBDLwwNZ1lKGm/dWb4Y9OD2DDCO9yPsxR37P6 mZ+xDGbmhkkxa2vNpaWIlbzwtMHTgh0WUdZ9CVddwnD/t+yKEbQmuouzc8YGkMueIb15LdRzRzc gUs6BWd0CzJIC6k= X-Google-Smtp-Source: AGHT+IEjPDdkm+wqc0/nQOIaUGfXCL2WaWk2kyN3+duInD0Cl29ECimZ0RwPanJoOY5BytdSZAn9lA== X-Received: by 2002:a05:6e02:1fcb:b0:3d0:137a:8ca2 with SMTP id e9e14a558f8ab-3d13e00afcamr67396595ab.22.1739060453235; Sat, 08 Feb 2025 16:20:53 -0800 (PST) Received: from [10.8.8.6] ([212.102.44.121]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-3d14c9c615asm6267105ab.55.2025.02.08.16.20.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 08 Feb 2025 16:20:52 -0800 (PST) Subject: Re: [gentoo-user] Question about compilation To: gentoo-user@lists.gentoo.org References: <2361441.ElGaqSPkdT@rogueboard> From: Dale Autocrypt: addr=rdalek1967@gmail.com; prefer-encrypt=mutual; keydata= mQINBGFSciYBEADcEGMyJBSuavKO/XKUVvgkxck7Nl8Iuu8N2lcnRji/rSKg5c1Acix1ll9i oW8JBCHwvn0+Xy60BvEsqcup3YSHw5STl/bR1ePEehtnYrg8FdjdS91+B805RfnKMm69rFVI wLSBHQrSG1yxHd8CloWoEdhmVtP24buajbh114bgXd9ahtpZrCVMrWdWYUg2mEXguGV5uNAh Rf8SWxDNc79w24JxsV34a8niMUYMjzWr0rafIbzk732X38vGjVMLo/2mMpkbp9mPp++LHoY+ 0Pet8zxxdXPJSCd475kza1AD+hhSyBZXB9yknYWgyY3cZe1rGmooJSi2KX4QxO7npwLThcO1 be6KKRkd35+Fi/a1BzVOHsZMiK/gcwxEFoMd27gir4ehaeHJfFXl+65w4hj0EsOZSxrJrm2C R50g5By2czSKP1bADEygFNpIJj51AR+wM88NImG2RPtlT2maYBzazvF05g65cdHXGp1C7W5P wwwKU2DgABB2t7N7z5A69LnryBRw4zUYDRRYLTYlBlYgg+xILm2c0OrBdxJgLJa7JE50Eo25 d3PFwt9J0gYvqy6sPFLl9So0sDg9zm0hKQtXOP5kgropUFGrNoJI+mjwF4rYLRBVzZwNAvlO OhEvHubBo3mEllv4x+FeptwXZxlk7gUsdqI8AxnFB8K9wi6FVQARAQABtBtEYWxlIDxyZGFs ZWsxOTY3QGdtYWlsLmNvbT6JAk4EEwEIADgCGyMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AW IQQSG1h01ruv/WNXc3Q3RqOgiQH1GwUCYVJy8gAKCRA3RqOgiQH1G+waEACeTZCt77jnRAmQ AV7otKuZekDWiLi3Eig8tj5ZJiCNSYA/hIxzmexRP0GMqjitcXK1iGwWcvMzzvIq30GAjIfB 4BR38cnXbtBa6fNewiT7QaZe/Hn6yBRldXNQypzbHy+/o27bUEy+oX4rE7etUgEHQAjuw7xz XFWg4tH1/KJvsOVY5upnWc5LdxYhsuQ3dQD4b22GsK0pOBDfb9PiirYM8eGKvrVuq4E/c75z lDDFhINl18lNZ9D0ZFL3IkTjHsAAqFH9uhnnEB8CWdHbBewPEfRaOhBUYWZ3Q8uTkmDgZT8q D9jlvLEdw7Nh2ApdxoepnI/4D+ql2Gr4DtH7SEPydr5gcf1Qr/2bXRb1hAYnIVcbncs/Bm3Z bkRKPVWMfE3Fusa+p5hMzixk0YysMaTHlc7mYRYAEZGnPMXnmcCbetwARU7A0yz1M1kCMOAQ Lsz8KH5kv3cRenMB6SFfjND2JfAK61H5TtnPq3L8noS2ZykRYxq9Nm3X64O1tJojIKBoZFr8 AwYNCvqC6puUyGMuzHPh7jPof8glfrrEKIYUvNPGMDoVX3IGetxh/9l6NcxgFA4JGoR+LS3C zmeNrwlllAe3OEUfKoWVQ+pagpSdM+8hHolaSda4Ys66Z3fCR4ZvcTqfhTAVskpqdXa4isAk 7vTcXu3L499ttywEp7rJTbkCDQRhUnImARAAncUdVhmtRr59zqpTUppKroQYlzR0jv8oa7DG K4gakTAT2N7evnI9wpssmzyVk8VEiLzhnFQ/Ol3FRt6hZCXDJt0clyHOyTfvz/MNFttWuZTc mLpSvmRR6VRjAH+Tz3Eam2xUw3PGuH97BcXQ3NnX3msv1UDxtxxBu6e2YrdeOhrCUSgzokcJ 98ChUNy934cgepPybAI12lSWqVFQ1aG7jExZfiUk+333fPSDbpKoZbTW5YJLXbycmW/C1IWL qYQyNjRWKaGoJtUWFhhmNiOQct7n90aKivNVPavmN+UQ9LlMaINtf9T6XCzLfogCFsulDCDJ 0yNQLDTurHaB4E71xoctgXmLLq9z1RQ0W2XiVAAOZQj6K3+d0AOUjDhCQ2QW8dUSq0ckkZXV DKVJOGS8Nhf2eIWIqRnP3AcUiiaiFGqUaVUmUAZ6h/oJmgghEu/1S+pcuUKU5i69+XCZ3hH2 Jzwzbf7K+FAIkOhCfHncF8i1N1pk00pOVykNnqHTfFo3qFusHt0ZWgXVnnn4pYdXqZNoDhvF BRE5Vm4k/k96Pw8HRx6Os6eFSRrlqGzRgqsu86FekxusXB9UGv4lJhtU/J+8MRWsh22K718s DbQnABicGKFz1qQlWvcf59oTByhLINJCBt1WXl+TzJDXepr3QSkqmK41dO9Hob97C9dMiK8A EQEAAYkCNgQYAQgAIAIbDBYhBBIbWHTWu6/9Y1dzdDdGo6CJAfUbBQJhUnLyAAoJEDdGo6CJ AfUbVHIQAKSWw620vPhR3A/njU2z77F3z/Jk+HTKdE3fIyWSWdkYN7CBFL0NguOMP30WZ+qE sJhZu7T5hf251MwQUUt27xlfnKYOmQs7CqONlXuXlGZI6WufrUjxNcVz+5gJsqvUWuuJWsgg sDmE92IBnfG/f81fPHWQyfr/SF4wYDMyoFp5xCCQpp1zB63iuFvvrhxBkEHzmbRtVDOhl0Xp BVEDR1w3QRACw9QJD/KM05Czv9JNQYlwinWO/OaQ9cMlUpKLgswUPg9IZ5vucxScfuAUA5uC B1jlAQ8ZPlVukBmbEv5RGOv+lpuEbA3YDMVtEeH4YMFbjt/+vH3Cr2vTbp5JlpByLburJEH0 WXZLUawEfUsZvVwpOuJK75vaa2HYXee+Cb3iCIzwfIfctdlqzUcbGRczlRNM59hpvj4z29Gh 3kAxVHItAYq54ikxQ9l4hQ8s9sLYPbX/WtcBxNX8crBSw0FLnmzGleVEtBHyqtt5CLzQNgrj GYWl1vKDUmRPw1CdZ1c+fMN9CY11jOM5B5ZnqZWfDeVYO2iJ5SuvTycChexCb8WYn1bdCBIo bBtga2RBXbVt4Mh9E4owsszefn51MwfjXxB20Fc5k3GU1AVpTCMs3ayYCzo0b2pvEvdjtDcA CYLEFPWgaFX9iQAM/CDfKvTtvgGWpqtCL2raq/mQoJEU Message-ID: <7166e50d-8bab-652d-80fb-bb954bff733a@gmail.com> Date: Sat, 8 Feb 2025 18:20:49 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <2361441.ElGaqSPkdT@rogueboard> Content-Type: multipart/alternative; boundary="------------81E9CAFB604520DBAEC1E90F" X-Archives-Salt: a766dde0-78fc-4141-af90-2a494170db11 X-Archives-Hash: fa7ee95400e88b45880afb231766a8c9 This is a multi-part message in MIME format. --------------81E9CAFB604520DBAEC1E90F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Michael wrote: > On Saturday 8 February 2025 23:07:38 Greenwich Mean Time Jack wrote: >> 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 >>> >>> 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. > You can run 'ebuild merge', but this will only continue with the > last package you were emerging when it was interrupted and it will continue > from whatever stage the emerge was at the time it was interrupted. > > If your intention is to suspend/hibernate the OS halfway through an emerge and > continue later on, then you can suspend the emerge job with job control: > > Ctrl+z > > After you wake up the system from suspend or reboot from hibernate you can > bring the emerge job back into the foreground, so it can continue running from > where you left it, by invoking: > > fg > > NOTE: Depending how many threads you were running before you suspended the > emerge and how much swap was being used, you may need to wait for a few > minutes for all the threads to pause. Keep an eye on top to confirm this has > taken place and the CPU is now idle, before you suspend/hibernate the OS. If > you don't you could discover the suspend/hibernate fails if you do not have > enough RAM/space. Would that survive a full reboot?  I'm asking about a regular desktop top system.  It's rare but sometimes I am doing updates and have a power failure and have to shutdown until power comes back.  I've always just done a emerge --resume but that starts any unfinished emerges from scratch.  Just curious if this would work.  If I can remember to do it if it does.  ;-)  Dale :-)  :-)  --------------81E9CAFB604520DBAEC1E90F Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Michael wrote:
On Saturday 8 February 2025 23:07:38 Greenwich Mean Time Jack wrote:

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.

You can run 'ebuild <package> merge', but this will only continue with the 
last package you were emerging when it was interrupted and it will continue 
from whatever stage the emerge was at the time it was interrupted.

If your intention is to suspend/hibernate the OS halfway through an emerge and 
continue later on, then you can suspend the emerge job with job control:

Ctrl+z

After you wake up the system from suspend or reboot from hibernate you can 
bring the emerge job back into the foreground, so it can continue running from 
where you left it, by invoking:

fg

NOTE:  Depending how many threads you were running before you suspended the 
emerge and how much swap was being used, you may need to wait for a few 
minutes for all the threads to pause.  Keep an eye on top to confirm this has 
taken place and the CPU is now idle, before you suspend/hibernate the OS.  If 
you don't you could discover the suspend/hibernate fails if you do not have 
enough RAM/space.


Would that survive a full reboot?  I'm asking about a regular desktop top system.  It's rare but sometimes I am doing updates and have a power failure and have to shutdown until power comes back.  I've always just done a emerge --resume but that starts any unfinished emerges from scratch.  Just curious if this would work.  If I can remember to do it if it does.  ;-) 

Dale

:-)  :-) 
--------------81E9CAFB604520DBAEC1E90F--