unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Sun, 24 Mar 2024 12:52:21 -0500	[thread overview]
Message-ID: <CAJf-WoQVRnFJrBsG_trE3EK8WyvbEkG1hSjUj-j6d_emyy0WvQ@mail.gmail.com> (raw)
In-Reply-To: <86edbzyavw.fsf@gnu.org>

Hi Eli :)

On Sun, Mar 24, 2024 at 9:14 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> The tarballs are signed; you can get the corresponding PGP signature
> files at:
>
>    https://ftpmirror.gnu.org/emacs/emacs-29.3.tar.xz.sig
>    https://ftpmirror.gnu.org/emacs/emacs-29.3.tar.gz.sig
>

I have been working on creating the WIndows binary distributions for
Emacs 29.3.  I typically make these using AOT native compilation (for
the benefit of users without libgccjit etc) however I'm not able to
get that to happen using the emacs-29.3 release tarball.

This is my configure + build formula:

./configure --with-modules --without-dbus
--with-native-compilation=aot --without-compress-install
--with-sqlite3 --with-tree-sitter CFLAGS=-O2 && make install V=1 -j 20
NATIVE_FULL_AOT=1 prefix=/rel/build/emacs-29.3 2>&1 | tee
../emacs-29.3_1.log

But I see relatively few ELN files:

  $ (cd /rel/build/emacs-29.3; find ./ -name '*.eln' | wc -l)
  155

Compare this with the number of ELN files when I build the emacs-29
branch from git (using ./configac && configure && make, rather than a
tarball provided configure script).

  $ (cd $( ls -1trd /h/install/emacs-30* | tail -1 ); find ./ -name
'*.eln' | wc -l)
  1589

Can you see something I'm doing wrong, or might there be a problem
here which prevents with-native-compilation=aot from doing it's thing
for a build from a release tarball?



  reply	other threads:[~2024-03-24 17:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 14:14 Emacs 29.3 released Eli Zaretskii
2024-03-24 17:52 ` Corwin Brust [this message]
2024-03-24 18:46   ` Eli Zaretskii
2024-03-24 19:36     ` Corwin Brust
2024-03-24 19:46       ` Eli Zaretskii
2024-03-24 19:58         ` Eli Zaretskii
2024-03-27  5:54         ` Corwin Brust
2024-03-24 18:48 ` Michael Albinus
2024-03-24 19:29   ` Eli Zaretskii
2024-03-24 20:10     ` Michael Albinus
2024-03-24 20:20       ` Eli Zaretskii
2024-03-26  8:48         ` Michael Albinus
2024-03-26 12:46           ` Eli Zaretskii
2024-03-26 14:28             ` Michael Albinus
2024-03-26 14:38               ` Ihor Radchenko
2024-03-26 17:50                 ` Michael Albinus
2024-03-26 18:01                   ` Ihor Radchenko
2024-03-26 18:48                     ` Michael Albinus
2024-03-26 19:35               ` Eli Zaretskii
2024-03-27  8:27                 ` Michael Albinus
2024-03-27 12:42                   ` Eli Zaretskii
2024-03-27 14:07                     ` Michael Albinus
2024-03-27 16:42                       ` Eli Zaretskii
2024-03-27 17:35                         ` Michael Albinus
2024-04-03 12:03                           ` Michael Albinus
2024-04-03 12:36                             ` Robert Pluim
2024-04-03 15:01                               ` Michael Albinus
2024-04-03 12:51                             ` Eli Zaretskii
2024-04-03 14:56                               ` Michael Albinus
2024-04-04 12:25                                 ` Eli Zaretskii
2024-04-04 12:40                                   ` Michael Albinus
2024-04-04 17:46                                   ` Ihor Radchenko
2024-03-27 15:15                     ` Corwin Brust
2024-03-26 15:32   ` Ulrich Mueller
2024-03-26 18:42     ` Michael Albinus
2024-04-06 15:45 ` Lynn Winebarger
2024-04-06 16:09   ` 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=CAJf-WoQVRnFJrBsG_trE3EK8WyvbEkG1hSjUj-j6d_emyy0WvQ@mail.gmail.com \
    --to=corwin@bru.st \
    --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).