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: master 05d240997a 2/2: Add native-compile-prune-cache command Date: Fri, 22 Jul 2022 13:51:04 +0000 Message-ID: References: <165675959499.8421.12451308740112322312@vcs2.savannah.gnu.org> <20220702105957.4B7EFC016B5@vcs2.savannah.gnu.org> <87bkthedix.fsf@gmail.com> <877d45b8sz.fsf@gmail.com> 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="24121"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, Lars Ingebrigtsen To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 22 15:56:33 2022 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 1oEt8r-00067D-9D for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Jul 2022 15:56:33 +0200 Original-Received: from localhost ([::1]:50026 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oEt8q-0007l0-1B for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Jul 2022 09:56:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48384) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oEt3e-0000Jp-GS for emacs-devel@gnu.org; Fri, 22 Jul 2022 09:51:10 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:62955) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oEt3c-0002KY-Ce for emacs-devel@gnu.org; Fri, 22 Jul 2022 09:51:10 -0400 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 26MDp38W006652 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 22 Jul 2022 13:51:03 GMT In-Reply-To: <877d45b8sz.fsf@gmail.com> (Robert Pluim's message of "Fri, 22 Jul 2022 15:01:32 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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" Xref: news.gmane.io gmane.emacs.devel:292435 Archived-At: Robert Pluim writes: >>>>>> On Fri, 22 Jul 2022 12:45:03 +0000, Andrea Corallo sa= id: > >> Should we wrap this (and perhaps `startup-redirect-eln-cache') in > >> (when native-comp-available-p) ? In a non-native compile Emacs they > >> signal an error: > > Andrea> Hi Robert, > > Andrea> do we support loading comp.el and using in non native builds? > > (require 'comp) > > certainly works (although you=CA=BCre right, the functions > in comp.el are not available by default, which means I must have > loaded comp.el myself at some point). > > Andrea> I thought is not the case, because otherwise most of the func= tions there > Andrea> ATM are probably broken for such a build no? > > Right. The question is if we want to support such a case (and if so, > exactly how). Yep, I really thought the answer was no, at least for now, but I might be wrong. BTW assuming the answer is no, should we add a load time check with associated error or warning for comp.el to gate all these possible issues? Thanks! Andrea