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

On Sun, Jan 01, 2023 at 10:39:00AM -0500, Eli Zaretskii wrote:

>  @itemize @bullet
>  @item
> -Emacs can no longer be built with support of native compilation of
> -Lisp programs.  This means Emacs builds much faster, and the problems
> -that came with native compilation: the need to have GCC and Binutils
> -installed, the complications of managing your @file{eln-cache}
> -directories---all of that is now future history.  The simplicity and
> -elegance of the Emacs byte-compiled code is now restored in all of its
> -pristine beauty.
> +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.

-- 
Sean Whitton



       reply	other threads:[~2023-01-03  6: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   ` Sean Whitton [this message]
2023-01-03 12:20     ` emacs-29 7fd822e7f5: Update Antinews in the user manual for Emacs 29 Eli Zaretskii

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=Y7PJOga2CnrboqsJ@athena.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).