unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 7fd822e7f5: Update Antinews in the user manual for Emacs 29
Date: Tue, 03 Jan 2023 14:20:35 +0200	[thread overview]
Message-ID: <83a62z24j0.fsf@gnu.org> (raw)
In-Reply-To: <Y7PJOga2CnrboqsJ@athena.silentflame.com> (message from Sean Whitton on Tue, 3 Jan 2023 06:20:42 +0000)

> Date: Tue, 3 Jan 2023 06:20:42 +0000
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: emacs-devel@gnu.org
> 
> On Sun, Jan 01, 2023 at 10:39:00AM -0500, Eli Zaretskii wrote:
> 
> > +Like its newer releases, Emacs 28 can still be built with support of
> > +native compilation of Lisp programs.  However, in preparation for
> > +removal of this feature in some previous version, we've deleted the
> > +capability of ahead-of-time native compilation of all the Lisp files
> > +that come with Emacs.  This makes the Emacs build process much faster.
> 
> I am pretty sure Emacs 28 can do the AOT compilation, but you have to export
> NATIVE_FULL_AOT rather than using a ./configure option.

Thanks, we will consider fixing this inconsistency in some past
version of Emacs, but it doesn't sound urgent, given that Emacs 27 is
currently planned to remove native compilation altogether anyway.



      reply	other threads:[~2023-01-03 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167258754001.27434.3439017790940062382@vcs2.savannah.gnu.org>
     [not found] ` <20230101153900.4FFB0C00A7F@vcs2.savannah.gnu.org>
2023-01-03  6:20   ` emacs-29 7fd822e7f5: Update Antinews in the user manual for Emacs 29 Sean Whitton
2023-01-03 12:20     ` 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=83a62z24j0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spwhitton@spwhitton.name \
    /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).