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: Sharing native-lisp system load-path between builds Date: Mon, 26 Jun 2023 05:31:09 +0300 Message-ID: <83edlzx8cy.fsf@gnu.org> References: <871qhzjd0m.fsf@thaodan.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9492"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?Q?Bj=C3=B6rn?= Bidar Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jun 26 04:32:01 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 1qDc1J-0002F4-45 for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Jun 2023 04:32:01 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qDc0G-0002ea-2C; Sun, 25 Jun 2023 22:30:56 -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 1qDc0B-0002eH-AG for emacs-devel@gnu.org; Sun, 25 Jun 2023 22:30:51 -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 1qDc0A-0006gE-F1; Sun, 25 Jun 2023 22:30:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=+XFgf+xcld/ZIOP3ek7vHPWNxvew8glnlEYgbr/8tM4=; b=P+0hvBPG7/SU1+Xyfq80 cdEl1D30mFSkiSc3KSp6hMDM9gQxs8/zcLlflsplf7mqo4u5qMiCw+Pf8a43K9S7tYROMrCevAJpS szxt0t81Rzd33V0vCMGxSMK8KPiBnoRctw8G6M9irnZYIkqGGNBRO3vJwmMfkXsKEaNccMlY6CMsH N05dOQhP3n9UMigYAzAApNspITdMNVQtNPzIdfVntOV6LK9nKtSSZE8J11rwqd6LW42cbbMBbxehy ReuTP2kcL/QXFekSaXIurp72gszDA//jlvyNJLAYeQJW1rUorfgIvmZPraeiQNP7oTbU1y0N1rGDd YYBEXU7t0ebQPw==; 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 1qDc09-000080-VN; Sun, 25 Jun 2023 22:30:50 -0400 In-Reply-To: <871qhzjd0m.fsf@thaodan.de> (message from =?utf-8?Q?Bj=C3=B6r?= =?utf-8?Q?n?= Bidar on Mon, 26 Jun 2023 03:14:17 +0300) 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:307222 Archived-At: > From: Björn Bidar > Date: Mon, 26 Jun 2023 03:14:17 +0300 > > I'm building Emacs master for OpenSUSE to provide testing. > OpenSUSE packaging packages Emacs so that they have three builds with > different feature sets: X11 without GTK, GTK and one build just without > X11 or GTK. > > This helps different users to chose their preferred builds and keeps > build workers small for Emacs packages build. > > The packages share the elisp, native-lisp ahead of time compilations and > docs. > > Recently the native-lisp load path changed to change per Emacs > executable. It isn't a recent change, at least not in principle. > I don't know the exact commit when this changed but it was > between ref 3c8167ec0f9647e6fc33e65b0a0324f96cb795ee and > d46a2fa319808963bbe8d3a90e7dbb13fcd844f5. > > Now my questions: Is this a bug or can a different hash be used to > determine the system load-path? It is very useful to precompile the > lisp code once per emacs builds that share the same code. It's impossible to share native-compiled *.eln files between different builds, because they depend on the primitives compiled into the build and on the architecture of the host CPU. So you must have a separate directory for each build configuration, and any significant change in the Emacs C code will require recompilation of all the *.eln files.