From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 7343b0d: ; * etc/NEWS: Native compilation is more picky about missing dependencies.
Date: Sat, 06 Nov 2021 19:25:18 +0200 [thread overview]
Message-ID: <83wnll9oxt.fsf@gnu.org> (raw)
In-Reply-To: <ba6ihb55q.fsf@fencepost.gnu.org> (message from Glenn Morris on Sat, 06 Nov 2021 12:49:37 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Sat, 06 Nov 2021 12:49:37 -0400
>
>
> > branch: emacs-28
> > commit 7343b0d0e4a1e665f99ea4473c1a4e4a13081e96
>
> > +Note that JIT native compilation is done in a fresh session of Emacs
> > +that is run in a subprocess, so it can legitimately report some
> > +warnings and errors that aren't uncovered by byte-compilation. We
> > +recommend examining any such warnings before you decide they are
> > +false.
>
> I would have hoped that it's well understood that byte compilation must
> be done in a separate Emacs process to be reliable, so that any previous
> definitions don't pollute the environment. This is not specific to native
> compilation.
It is understood by us, but not by people out there, who are routinely
compiling their init files from sessions that have other files loaded.
> If this NEWS entry means nothing deeper than that, I find it a bit
> misleading.
I don't know if it's deeper, but it doesn't mean to say what you think
it does, and it isn't directed at the Emacs developers.
prev parent reply other threads:[~2021-11-06 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211106130424.4645.53189@vcs0.savannah.gnu.org>
[not found] ` <20211106130425.7CD8120A22@vcs0.savannah.gnu.org>
2021-11-06 16:49 ` emacs-28 7343b0d: ; * etc/NEWS: Native compilation is more picky about missing dependencies Glenn Morris
2021-11-06 17:25 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wnll9oxt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).