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.devel Subject: Re: Org mode update breaking build? Date: Tue, 09 May 2023 22:07:43 +0300 Message-ID: <83jzxh9vcw.fsf@gnu.org> References: <00b52cc1-b0ac-a0c0-c91d-33a7213e9881@web.de> <83v8h9l5cw.fsf@gnu.org> <87lehx4g6i.fsf@gnu.org> <83v8h1a1uv.fsf@gnu.org> <87h6sl4e6v.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31263"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: sds@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 09 21:07:35 2023 Return-path: Envelope-to: ged-emacs-devel@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 1pwSgQ-0007zr-R9 for ged-emacs-devel@m.gmane-mx.org; Tue, 09 May 2023 21:07:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pwSfY-0000h7-Gj; Tue, 09 May 2023 15:06:40 -0400 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 1pwSfX-0000dd-AU for emacs-devel@gnu.org; Tue, 09 May 2023 15:06:39 -0400 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 1pwSfW-0004P1-W1; Tue, 09 May 2023 15:06:39 -0400 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=nj1guPlsUyhCE+7lYqhYaXRuxdNKzjEZCMfd9kl/bmY=; b=onyTFpSSgaEK Um6+ywGrkLS8MKFleNmA9LRhrLNLT9CKHo91eCWrvMcygNJnpenvSZtBtUVfAQ7bOZyqNFdWiiRn9 tje0LEf4/hF5aEDfrEMCB70j0Rhkinf/rttKlo7RotoJwDiYmlyXNYxk+dtd/H12+KP+mw/lX28zo U3UFb1zh8bx4dPTTVrL092fwiFjBfp5vFSCQZMK092MdKEwdmvHJ0Ni6YMK5572K8lsiut5AJdddb DLQ2gx7w8yJ1r32I68a8wy4KblsmKZy4LB3xwjrJrRGDy4EiXhrPK7gLTk4R7GDXY3PqfGWieUB9f s6zk35r3BnpGcl1ECONU2w==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pwSfW-00085Z-KU; Tue, 09 May 2023 15:06:38 -0400 In-Reply-To: <87h6sl4e6v.fsf@gnu.org> (message from Sam Steingold on Tue, 09 May 2023 13:17:28 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306014 Archived-At: > From: Sam Steingold > Date: Tue, 09 May 2023 13:17:28 -0400 > > >> Basically, an apparently successful build no longer guarantees that > >> the resulting Emacs will be working. > > > > That was never guaranteed. Not just when Org changed. > > I have never seen this before, sorry. I guess you don't rebuild Emacs frequently enough. > > Feel free to propose how to detect this, and then restart, without > > disrupting the whole build. We are not just compiling Org, we compile > > hundreds of Lisp files, so whatever you propose should be consistent > > with how the normal build proceeds, including its support for high > > parallelism. If a better solution will be found, we will surely > > embrace it. > > I can describe how CLISP handles this: > (https://clisp.sourceforge.io/impnotes/require.html#lib-files > and https://lists.gnu.org/archive/html/emacs-devel/2021-10/msg00274.html) > > Compilation of `foo.el` should produce 2 files: > > 1. `foo.elc`, as now - this is the code whose loading is functionally > equivalent to loading `foo.el`. > > 2. `foo.elh` ("header") - this contains only the compile-time > dependencies (i.e., compiled `defvar`, `defconst`, `defmacro`, and > `defsubst` definitions and function declarations), > > When the compiler sees `(require 'foo)`, it will check whether `foo.elh` > has changed since last loaded and will reload it automatically. > Note that `foo.elh` is (probably) much smaller than `foo.elc` and thus > cheaper to load. > > For "pre-built" files like `subr.el` (which no other file ever requires): > when `subr.el` is recompiled, we check whether `subr.elh` has changed, and, > if it did, everything needs to be recompiled. > If it did not, no action is necessary. The general idea is simple, indeed, but there are rocks under the surface. See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62762#206 for the description of some of them.