unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The emacs-28 release branch has been created
Date: Sun, 3 Oct 2021 13:14:15 -0400	[thread overview]
Message-ID: <10401c4a-1d0a-817c-942e-f08ab3130552@cornell.edu> (raw)
In-Reply-To: <83a6jq84wu.fsf@gnu.org>

On 10/3/2021 12:11 PM, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Ken Brown <kbrown@cornell.edu>
>> Date: Sun, 3 Oct 2021 11:34:31 -0400
>>
>>>>      HAVE_NATIVE_COMP = @HAVE_NATIVE_COMP@
>>>
>>> I think it's supposed to get that from the top-level Makefile.
>>> Doesn't it do that in your builds?
>>
>> No.  And both lib/Makefile.in and lisp/Makefile.in include that line.
> 
> Oops!  Should be fixed now, thanks.

I built a tarball and started testing, and I found another bug, this one 
somewhat non-intuitive: In the recipe for ../native-lisp, "mkdir" needs to be 
replaced by "$(MKDIR_P)" (or even omitted).  The reason is that the native-lisp 
directory actually exists by the time that recipe is executed.

Suppose you run "make all" in src and the native-lisp directory doesn't exist. 
Make sees that the prerequisite "../native-lisp" of "all" doesn't exist, so it 
remembers that it will have to build it after building emacs$(EXEEXT), $(pdmp), 
and $(OTHER_FILES).  But by that time native-lisp exists because of "make 
compile-first" in the lisp directory.

Here's what I see in my build log before making the change:

./temacs --batch  -l loadup --temacs=pbootstrap \
	--bin-dest /usr/local/bin/ --eln-dest /usr/local/lib/emacs/28.0.60/
[...]
make -C ../lisp compile-first EMACS="../src/bootstrap-emacs.exe"
make[2]: Entering directory '/tmp/emacs-28.0.60/lisp'
   ELC+ELN  emacs-lisp/comp.elc
   ELC+ELN  emacs-lisp/comp-cstr.elc
[...]
LC_ALL=C ./temacs -batch  -l loadup --temacs=pdump \
	--bin-dest /usr/local/bin/ --eln-dest /usr/local/lib/emacs/28.0.60/
[...]
/usr/bin/mkdir ../native-lisp && make --no-print-directory 
../lisp/emacs-lisp/autoload.eln ...

... and the mkdir command fails.

After making the change, the native compilation of the preloaded files proceeds, 
and I think everything will be OK.  I say "I think", because I ran into fork 
failures (even on 64-bit Cygwin!), so I'll need to insert rebase commands 
somewhere before I can test further.

Ken



  reply	other threads:[~2021-10-03 17:14 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 [this message]
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

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=10401c4a-1d0a-817c-942e-f08ab3130552@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).