From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Sun, 24 Mar 2024 21:46:03 +0200 [thread overview]
Message-ID: <86ttkvjtvo.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoT2YgcDJHWBhU8N+r2EhamNyF0XiBzx8yq_eAW8a3-j+Q@mail.gmail.com> (message from Corwin Brust on Sun, 24 Mar 2024 14:36:08 -0500)
> From: Corwin Brust <corwin@bru.st>
> Date: Sun, 24 Mar 2024 14:36:08 -0500
> Cc: emacs-devel@gnu.org
>
> > I have no idea. Comparing the configure script for Emacs 29.2 and
> > Emacs 29.3 doesn't show any differences, and neither does comparing
> > the various Makefile's.
> >
> > If you build Emacs 29.2 in this manner, do you get all the *.el files
> > compiled into *.eln, or do you see the same problem with Emacs 29.2?
>
> No, Building 29.2 from the release tarball (so, without running
> autogen.sh) successfully precompiles all the ELNs as expected.
Strange. I don't see this problem.
> > One note, though: if you say --with-native-compilation=aot, you don't
> > need the NATIVE_FULL_AOT=1 part. Not sure if this is relevant or not.
> >
>
> A good point. I haven't tried removing this to see if anything
> changes; 29.2 works properly, so I suspect this is a read herring but
> I'll try removing it, nevertheless.
>
> I do get all full AOT build if I add ./autogen.sh to the start of my
> recipe -- which is really weird. I find no differences between the
> configure script provided with emacs-29.3 tarball and the one created
> by running autogen.sh against the unpacked release tarball sources. I
> have no idea why AOT is working in the latter case but not the first.
FWIW, I've just built the 29.3 release tarball with the
"--with-native-compilation=aot" option (and without
NATIVE_FULL_AOT=1), and it builds all the *.eln files just fine. I
didn't need to run autogen.sh.
> I'm inclined to go ahead and publish using the version where I run
> autogen.sh -- let me know if we prefer that we track this issue down
> first, instead.
I don't think autogen.sh can do any harm, but I cannot be sure without
understanding why you see this weird problem.
next prev parent reply other threads:[~2024-03-24 19:46 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
2024-03-24 18:46 ` Eli Zaretskii
2024-03-24 19:36 ` Corwin Brust
2024-03-24 19:46 ` Eli Zaretskii [this message]
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=86ttkvjtvo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=corwin@bru.st \
--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).