From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" Date: Wed, 01 Jan 2025 20:52:03 +0200 Message-ID: <86r05ml63w.fsf@gnu.org> References: <878qrxgg74.fsf@Phoenix> <864j2lnf1j.fsf@gnu.org> <87zfkddk1l.fsf@Phoenix> <86zfkdlz39.fsf@gnu.org> <87a5camnyu.fsf@protonmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30465"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, 75209@debbugs.gnu.org, njackson@posteo.net To: Pip Cet Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 01 19:53:45 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tT3qj-0007oB-71 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 01 Jan 2025 19:53:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tT3qA-0007cY-Cl; Wed, 01 Jan 2025 13:53:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tT3q3-0007bm-Ca for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 13:53:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tT3q3-0005no-3U for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 13:53:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=nKk3kmSjb2zZi1ezb8dX+hB6lwtz5A7I5sbpbMVKM58=; b=iQZdCrFZ0aWVOD7ZXCHeFp3BisM4WdiHQbmhDnHh+0DIydbVCam0gFaoPHuy4ySOqkhlNeJmXiwb7rdVV71+v0qXGlO0LdvICcPU0vlzMX+glPKeXFpRSkQVmD9p4kRPh3MnV1UX8CazK6sxhnXlF7KaB6k+XQhZrsUpWWEQ3ehKcilr1IioYKg5PLfq67rthDylSTjVr7L5RcWvorjr/kA7/RcjLOSmQDFfVa+yitdcr80RE2FJ2KrJzZe+ZppklwpcFlIjBKC6yE3IIIXHCGWll9tZ7rOCklpW5o8XTedISYqwkGWGrR7u4rYuLbv/ekSvoUJJl4fl/VUUsR4Niw==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tT3q2-0006Oj-V9 for bug-gnu-emacs@gnu.org; Wed, 01 Jan 2025 13:53:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 01 Jan 2025 18:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75209 X-GNU-PR-Package: emacs Original-Received: via spool by 75209-submit@debbugs.gnu.org id=B75209.173575753624491 (code B ref 75209); Wed, 01 Jan 2025 18:53:02 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 1 Jan 2025 18:52:16 +0000 Original-Received: from localhost ([127.0.0.1]:39790 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tT3pI-0006Mx-C0 for submit@debbugs.gnu.org; Wed, 01 Jan 2025 13:52:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35222) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tT3pG-0006MW-C4 for 75209@debbugs.gnu.org; Wed, 01 Jan 2025 13:52:15 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tT3p9-0005fJ-CB; Wed, 01 Jan 2025 13:52:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=nKk3kmSjb2zZi1ezb8dX+hB6lwtz5A7I5sbpbMVKM58=; b=enlSOCwL6Z8S bLPjbPIm5578g7Cgu79QqGPxfJA9SSetgZOAy8P60xDqc/O5V7y9I2RwhkJjZj2H56v8W9R2sMoFX ySiXxF3PN3KzRN4+uFtNNhLZR8S5wm6gmDviICR0/Mgv7br3WBpRt7Hew63xun0YVdKC8ULneZRkC D9kgwpzSFCxbnQpSKgauf04uBtbgPuxnKQKTydYMW+rONmL16XxrNOE8E9hsmVYgTYXR9KQzN9UeC yNxB1cyotiXVIfjdxMuap6yVfhbrtKchhgMVeanorN+h0CeCfdWWTKUGtz3rXh4sntb/Fzyyyw0fk NKx2Jhb2oWo/tIfpBZVP2w==; In-Reply-To: <87a5camnyu.fsf@protonmail.com> (message from Pip Cet on Wed, 01 Jan 2025 17:41:57 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298069 Archived-At: > Date: Wed, 01 Jan 2025 17:41:57 +0000 > From: Pip Cet > Cc: "N. Jackson" , yantar92@posteo.net, 75209@debbugs.gnu.org > > I'm assuming that the resolution was that the file was read before we > finished writing it. I've run into the same issue a number of times > (interrupting and resuming Emacs builds leads to build failures, "make > bootstrap" makes them go away). > > Can we consider modifying the .elc format to have a footer indicating > that the file is complete? The .elc file is supposed to be created only when the compilation is complete and successful. If you look at byte-compile-file, you will see that we first compile the Lisp code, then write the produced bytecode to a temporary file, and only after that we rename the temporary file into the target .elc file. Renaming a file is an atomic operation on Posix filesystems, so it either completely succeeds or completely fails. We only write directly to the target file if that file's directory is unwritable. So I don't understand why you see incomplete .elc files when you interrupt the build. What happens in my case is that I see those temporary files left around, but I don't think I've ever saw an incomplete .elc file after interrupting the build. Is it likely that the directory where you build Emacs is not writable by your user? That's the only way I could explain what you see. Or maybe there's some other factor at work here, in which case we should find out what that factor is, before we consider how to fix it. In any case, I think this is a separate issue, so I'd prefer to have a separate bug report for it. Thanks.