From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: [External] : Re: Native compilation Date: Mon, 10 Jan 2022 14:23:12 +0100 Message-ID: <87tuebsp1b.fsf@zoho.eu> References: <875yr5up38.fsf@zoho.eu> <83k0flge7s.fsf@gnu.org> <87tuept0qc.fsf@zoho.eu> <83ee5tgcwv.fsf@gnu.org> <87ilv5sz9s.fsf@zoho.eu> <834k6ohp2o.fsf@gnu.org> <87ilutv5sb.fsf@zoho.eu> <83czl12xgd.fsf@gnu.org> Reply-To: Emanuel Berg Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21003"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:V5cbFixedmYco7p4HUH5WIGXEe0= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 10 14:36:04 2022 Return-path: Envelope-to: geh-help-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 1n6uqC-0005Bz-N5 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 10 Jan 2022 14:36:04 +0100 Original-Received: from localhost ([::1]:55742 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n6uqB-0002fh-71 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 10 Jan 2022 08:36:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58934) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n6udx-0002EW-TU for help-gnu-emacs@gnu.org; Mon, 10 Jan 2022 08:23:25 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:40674) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n6udw-000256-0S for help-gnu-emacs@gnu.org; Mon, 10 Jan 2022 08:23:25 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1n6udt-0008OM-QF for help-gnu-emacs@gnu.org; Mon, 10 Jan 2022 14:23:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135178 Archived-At: Eli Zaretskii wrote: >>>> Here is what it said during the native compile: >>>> >>>> Warning (comp): Cannot look-up eln file as no source file >>>> was found for /home/incal/.emacs.elc >>> >>> The former means your .emacs was not natively compiled >>> (which is generally a Good Thing). >> >> Thanks, you mean not to compile it natively or not compile >> it at all? > > Natively. Okay, it is interesting that you say so because didn't you use (?) to say that byte-compiling of the .emacs and supplemental files was disencouraged? Well, I meet you half the way since one of the big advantages with byte-compilation is that it gives you an easy way to improve the quality of the code, and with native byte-compile, you don't get that advantage since you already got it with ordinary/universal byte-compile ... >> But the strange thing is it _is_ compiled, there is an >> .emacs.elc which according to file(1) is "Emacs/XEmacs v28 >> byte-compiled Lisp data", however the Emacs that compiled >> [1] it is actually > > The native compilation didn't happen because Emacs didn't > find the source file for the .elc file. I'm saying that you > shouldn't worry about that: native compilation of init files > can only cause trouble, and will never provide any tangible > performance boost. So just disregard that warning. > >> So I wonder if there is some special way to compile >> it natively? > > Maybe. But why bother? Well, we we are into technology unless you didn't notice. Why is it that while it makes sense to natively byte-compile the Elisp of GNU Emacs it doesn't make sense to natively byte-compile all other Elisp? But OK, just byte-compiling the old what, that doesn't make it natively byte-compiled, right? That happens automatically when Emacs is run, after being configured --with-native-compilation [1], and it only affects GNU Emacs Elisp, right? Or what about [M]ELPA Elisp, that natively byte-compiled as well? If so, even more so, then why not all Elisp? >> It is in the MELPA's Emacs-w3m, I think, version 1.4.632. > > Report a bug to the developers. I CC the previous post to gmane.emacs.w3m ... there is no common interface to submit bugs in random Elisp software I guess? :) [1] https://dataswamp.org/~incal/conf/.zsh/install-emacs -- underground experts united https://dataswamp.org/~incal