From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Sharing native-lisp system load-path between builds Date: Wed, 16 Aug 2023 04:49:21 -0400 Message-ID: References: <871qhzjd0m.fsf@thaodan.de> <83edlzx8cy.fsf@gnu.org> <87jzvqj1d0.fsf@thaodan.de> <87il9i5wtw.fsf@thaodan.de> <83pm3qbbkr.fsf@gnu.org> <87il9i3ppl.fsf@thaodan.de> <83bkf9bylz.fsf@gnu.org> <87bkf932b5.fsf@thaodan.de> <83zg2ta2kp.fsf@gnu.org> <87wmxv5t3p.fsf@thaodan.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3697"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Eli Zaretskii , 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 Wed Aug 16 10:50:47 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 1qWCEo-0000ny-76 for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Aug 2023 10:50:46 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qWCDx-0002tI-Ix; Wed, 16 Aug 2023 04:49:53 -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 1qWCDj-0002nq-Hz for emacs-devel@gnu.org; Wed, 16 Aug 2023 04:49:48 -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 1qWCDi-0000kD-BW; Wed, 16 Aug 2023 04:49:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=7XTcGTg+98fh1Yt16HWotSSL0XipZe+wZXNFiDtdYCs=; b=YNAcuy0oHQcj1sujdGhg 1g+HTS2fgvVcAyqj9WQIUzdfW3hUxVEtvKQ7lGbqkHg+E9xSyiTA/ihAZ3eDPum7F9EwBXBMlwDN8 yKKVlLd0TJZm/sJABw84tBhAEVsmKUcNnDqcegpo2a71ZuNuD6CmoJ/qHGN21qUKBO0A1iRNWFIwf lwz3VtwpjqGmhg9QD5WLlL7t5H2gSanXp2cdCQnBlyEqseqZM13S0LWnvcWrpFyWpwiCLGBIfQvBH 2vfQ/RD6iKd1u1OtbVaY3dqtvcJd90qifQMsy33aqb11L8wbaDkJXRdYlgWvELss/ypzGRk/qTuR6 lmI7fBuCYgVdDA==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1qWCDV-0008J9-49; Wed, 16 Aug 2023 04:49:35 -0400 In-Reply-To: <87wmxv5t3p.fsf@thaodan.de> (=?utf-8?Q?=22Bj=C3=B6rn?= Bidar"'s message of "Wed, 16 Aug 2023 10:44:42 +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:308801 Archived-At: Bj=C3=B6rn Bidar writes: > Eli Zaretskii writes: > >>> From: Bj=C3=B6rn Bidar >>> Date: Mon, 14 Aug 2023 21:29:34 +0300 >>>=20 >>> Eli Zaretskii writes: >>>=20 >>> > Thanks. So what does "work" and "does not work" mean in this context? >>>=20 >>> Work means the eln files could be shared, doesn't mean the files can't >>> be shared the hash in the native lisp path is different and the files >>> are no longer compatible. >> >> How did you share them? did you manually copy them into the same >> directory or forced Emacs to write them there? Or did Emacs create >> *.eln files with the same hashes and in the same 29.0.50-NNNNN >> subdirectory? > Yes exactly. The - directory was the same. > >> Also, which *.el files were compiled into *.eln files >> you could share -- were those the preloaded *.el files, non-preloaded >> *.el files from the Emacs tree, or third-party *.el files from >> packages that are not bundled with Emacs? > Only the builtin el files as can be seen in the spec file. > >>In general, such different configurations could only be able to share >>*.eln files by sheer luck. It is enough to have one more or one less >>primitive in one of the builds to require a separate set of *.eln >>files, because the hash of the versioned subdirectory of native-lisp/ >>and of eln-cache changes when primitives are added or deleted. That >>has been so for a very long time, definitely long before commit >>3c8167ec0f964. > > Does enabling or disabling lets say png change any of those > primitives? Yes Andrea