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)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C79181582EF for ; Sat, 08 Feb 2025 23:08:47 +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 A9E503430C2 for ; Sat, 08 Feb 2025 23:08:47 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 43AE811047E; Sat, 08 Feb 2025 23:07:43 +0000 (UTC) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) (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 1F5041103CB for ; Sat, 08 Feb 2025 23:07:41 +0000 (UTC) Received: by mail-qv1-f53.google.com with SMTP id 6a1803df08f44-6e440e64249so32905336d6.3 for ; Sat, 08 Feb 2025 15:07:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739056061; x=1739660861; h=content-transfer-encoding:content-disposition:message-id :in-reply-to:mime-version:to:subject:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7cQ2q7l/wz3GIvno4rSyS4EjsLIDETHWJ890mx4nUio=; b=qXGDZjPKHmRo34kABFG4QavntRrmBKigOSfVOjLO4uS1WPkskb2bbs/Cx4qxJBnQ8S qLo3yUfbjKsWByfdkS4LDLl8PHgzUSZpjb1z7dmgixv9OEq91PFsjIHku8uARK8ftAd5 TiKKLTVDrrVpRii9BCAxSzYPy+gjDBMo8WyHiTUpMWJPHMMBSSuGsCNLEvBoaiqZG9QR EyABhT9UtQAXfAXQolIx54TO8xvubQoLbX4xvK3YnST5WCzlDmkWCWM1YZxtR0Mlbp3l D1B97rd8EHtIVwUADujC99FAumPVnfcU/YYGdp7xDWaqgFX1pyFHVQ2kgPgh6dSd6hUQ F8KA== X-Gm-Message-State: AOJu0YyUlmREY/UdEFTLoDCNH9S6HEmu6127a/9q5I649XOpmsuc2/gM uEyoNrZMbayeB0BelXQsW0av9Npz5nc8eoF+gJI3AcjwmoGkL34pefKpVp8qNSmg5IsUFD4Yi0T 0H70= X-Gm-Gg: ASbGncv1/PT+GT2ucG3cGLOng3FHUQVo1AmjWM/EaLfkpeZFCj4Oi9/ofJGNO0XorHO 87PWluczUkAhmCviscxxXlIcDFcL9OFqLb5UUc1d2wf7CKtZeOhTXLpRsgpy4U5eXCeJLJG2MVB mKphSR6g0pdc8TyG3IvnkciVyqNflvUdPuIxiUNXJNsMo7xV3lUDL8S7pXsbIlfpBQBR+VdhoiR 95W8OiR6B4Zn2rp9Rd9z6sqIPE7ZRL8ySr94I1kzhYknBrPyJfd2Ady8uWMrYv3+D+b/EBKJCzg nLOmh9qrLZarvTQH7oIfJ0axaBLQYH92M/DuYg8erJsKYpgPMoa1rxM9hvSsYbfaOXhW7+GzyLf BCg== X-Google-Smtp-Source: AGHT+IEfLgEchGCWgOB0nu4eYVgvbmkULcudWDtadHT2D7s4NKl+GzEpBrjHYkmFOTkDDa3dLcE2Sw== X-Received: by 2002:ad4:5dea:0:b0:6e4:1e16:b63d with SMTP id 6a1803df08f44-6e44563af59mr116997256d6.21.1739056060844; Sat, 08 Feb 2025 15:07:40 -0800 (PST) Received: from ffortso9 (32-223-239-183.bng01.wlmn.ct.frontiernet.net. [32.223.239.183]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6e4453a1ce3sm22639406d6.57.2025.02.08.15.07.38 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 08 Feb 2025 15:07:39 -0800 (PST) Date: Sat, 08 Feb 2025 18:07:38 -0500 From: Jack Subject: Re: [gentoo-user] Question about compilation To: gentoo-user@lists.gentoo.org 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: X-Mailer: Balsa 2.6.4-240-ge8672f804 Message-Id: Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b515972d-5b01-45cd-88e1-2a1f6bc6e92c X-Archives-Hash: 5ad5e08f34979c024d4eb8c58aaa9f89 On 2025.02.08 14:00, Filip Kobierski wrote: > Hi Jacques, >=20 > 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 >=20 > Regards > Filip >=20 > On Saturday, February 8th, 2025 at 15:47, Jacques Montier =20 > wrote: >=20 > > Hello everyone, > > Is it possible to stop a compilation midway in the case of a very =20 > long compilation and then resume it from the same point without =20 > having to start over from the beginning ? > > Thank you for your response. > > Best regards, > > > > -- > > Jacques Montier. >=20 If you really mean just interrupting a compile, then you should be able =20 to stop with Ctl-C, and then start/continue by running make or ninja =20 again, assuming that is what is used for whatever you are compiling. =20 Ccache can help since most of the results of the previous compile =20 attempt will have been cached, and so will be completed more quickly =20 the next time, but it's not the same as continuing from where it was =20 interrupted. If, as Filip implies, you are asking about interrupting emerge, it's =20 easy enough to interrupt, but essentially impossible to continue from =20 where it left off. "emerge --continue" will just try to emerge every =20 package from the interrupted emerge which was not completed, but it =20 will start each one from scratch. What has often, but not alwasy =20 worked for me, is to use ebuild directly. "ebuild =20 .../path/to/package.ebuild compile" will figure out that everything =20 prior to the compile was completed, and then issue the make or ninja =20 commands, which will just pick up where they left off. If that does =20 work, then you need to repeat the ebuild, but with the install and then =20 the qmerge commands. The only problem with that (for me, at least) is =20 that ebuild does not leave exactly the same lines in emerge.log, so a =20 package installed that way will not show up in "gentlop -t package" =20 output.