From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: emacs-devel@gnu.org
Subject: Re: The emacs-28 release branch has been created
Date: Mon, 04 Oct 2021 16:34:20 +0300 [thread overview]
Message-ID: <831r507w2r.fsf@gnu.org> (raw)
In-Reply-To: <d17f3468-f5eb-48a9-ee49-0547c3566a35@cornell.edu> (message from Ken Brown on Mon, 4 Oct 2021 09:11:35 -0400)
> Cc: emacs-devel@gnu.org
> From: Ken Brown <kbrown@cornell.edu>
> Date: Mon, 4 Oct 2021 09:11:35 -0400
>
> > # TARGETS is set dynamically in the recursive call from 'compile-main'.
> > # Do not build comp.el unless necessary not to exceed max-specpdl-size and
> > # max-lisp-eval-depth in normal builds.
>
> Maybe I'm misunderstanding the comment, but if byte-compiling comp.el and
> comp-cstr.el causes max-specpdl-size and max-lisp-eval-depth to be exceeded,
> isn't that a problem for builds with native compilation that needs to be fixed?
No, because the problem doesn't happen in builds with native
compilation, AFAIK.
> If I'm wrong, that's fine, but then it means that the instructions for making a
> tarball have to be changed to ensure that those two files get byte-compiled for
> the tarball.
The tarball should be built from Emacs configured with native
compilation, that's true. Something to mention in make-tarball.txt, I
guess.
prev parent reply other threads:[~2021-10-04 13:34 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 18:30 The emacs-28 release branch has been created Eli Zaretskii
2021-10-02 15:58 ` Windows Binaries Release: was The emacs-28 release branch Phillip Lord
2021-10-03 10:53 ` Po Lu
2021-10-04 19:04 ` Phillip Lord
2021-10-16 20:24 ` Konstantin Kharlamov
2021-10-17 0:43 ` Po Lu
2021-10-17 13:45 ` Konstantin Kharlamov
2021-10-20 15:26 ` Phillip Lord
2021-10-03 11:22 ` Corwin Brust
2021-10-04 19:05 ` Phillip Lord
2021-10-16 10:03 ` H. Dieter Wilhelm
2021-10-16 13:31 ` Corwin Brust
2021-10-16 16:01 ` H. Dieter Wilhelm
2021-10-20 15:24 ` Phillip Lord
2021-10-20 18:36 ` H. Dieter Wilhelm
2021-10-27 19:36 ` H. Dieter Wilhelm
2021-10-27 21:07 ` Phillip Lord
2021-11-01 20:47 ` H. Dieter Wilhelm
2021-11-01 21:06 ` Óscar Fuentes
2021-11-02 11:16 ` Eshell requires execute permission on Win10, was " H. Dieter Wilhelm
2021-11-02 14:37 ` Óscar Fuentes
2021-11-02 18:57 ` MinGW Sources, was: Windows Binaries Release H. Dieter Wilhelm
2021-11-02 19:07 ` Óscar Fuentes
2021-11-04 17:51 ` H. Dieter Wilhelm
2021-11-08 22:27 ` Phillip Lord
2021-11-09 12:25 ` Eli Zaretskii
2021-11-09 14:32 ` Phillip Lord
2021-11-02 10:47 ` Windows Binaries Release: was The emacs-28 release branch Phillip Lord
2021-11-02 12:05 ` H. Dieter Wilhelm
2021-10-20 15:16 ` Phillip Lord
2021-10-21 0:13 ` Corwin Brust
2021-10-27 21:11 ` Phillip Lord
2021-10-03 1:35 ` The emacs-28 release branch has been created Ken Brown
2021-10-03 6:53 ` Andreas Schwab
2021-10-03 9:27 ` Eli Zaretskii
2021-10-03 15:01 ` Ken Brown
2021-10-03 15:17 ` Eli Zaretskii
2021-10-03 15:34 ` Ken Brown
2021-10-03 16:11 ` Eli Zaretskii
2021-10-03 17:14 ` Ken Brown
2021-10-03 17:33 ` Eli Zaretskii
2021-10-03 17:49 ` Eli Zaretskii
2021-10-03 17:56 ` Ken Brown
2021-10-03 18:03 ` Eli Zaretskii
2021-10-03 19:20 ` Eli Zaretskii
2021-10-03 19:42 ` Eli Zaretskii
2021-10-03 19:45 ` Ken Brown
2021-10-03 21:21 ` Ken Brown
2021-10-03 22:40 ` Ken Brown
2021-10-04 18:51 ` Eli Zaretskii
2021-10-04 13:31 ` Ken Brown
2021-10-04 14:25 ` Eli Zaretskii
2021-10-04 14:39 ` Eli Zaretskii
2021-10-04 14:45 ` Andrea Corallo via Emacs development discussions.
2021-10-04 14:54 ` Eli Zaretskii
2021-10-04 15:13 ` Andrea Corallo via Emacs development discussions.
2021-10-04 16:15 ` Andrea Corallo via Emacs development discussions.
2021-10-04 16:58 ` Eli Zaretskii
2021-10-04 19:38 ` Andrea Corallo via Emacs development discussions.
2021-10-04 19:40 ` Andrea Corallo via Emacs development discussions.
2021-10-04 19:54 ` Eli Zaretskii
2021-10-04 21:58 ` Ken Brown
2021-10-05 11:43 ` Eli Zaretskii
2021-10-05 15:43 ` Andrea Corallo via Emacs development discussions.
2021-10-05 11:29 ` Eli Zaretskii
2021-10-05 15:37 ` Andrea Corallo via Emacs development discussions.
2021-10-05 16:14 ` Eli Zaretskii
2021-10-05 16:52 ` Andrea Corallo via Emacs development discussions.
2021-10-05 17:12 ` Eli Zaretskii
2021-10-04 11:37 ` Eli Zaretskii
2021-10-04 13:11 ` Ken Brown
2021-10-04 13:34 ` 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=831r507w2r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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).