unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 26459@debbugs.gnu.org
Subject: bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull"
Date: Fri, 14 Apr 2017 21:25:36 -0400	[thread overview]
Message-ID: <5ak26mpilr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <9yinm73if2.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 13 Apr 2017 21:08:17 -0400")

Glenn Morris wrote:

> IIUC, making lisp's gen-lisp also generate the unidata files (as well as
> leim and semantic) ought to fix your issue? In fact, I'm not sure why I
> didn't do that - maybe it turns out not to be so straightforward.

I find the following patch causes my -j8 builds to often hang forever
(prior to 28718c4), because two Emacs processes try to modify eg
uni-name at the same time. I don't know why Make apparently spawns two
jobs at the same time to do the same thing. Possibly because
admin/unidata/Makefile doesn't explicitly list the output uni*.el files,
and calls make in a loop. Maybe we should improve that.


--- i/lisp/Makefile.in
+++ w/lisp/Makefile.in
@@ -347,9 +347,9 @@ compile-clean:
 	  fi \
 	done
 
-.PHONY: gen-lisp leim semantic
+.PHONY: gen-lisp leim semantic unidata
 
-gen-lisp: leim semantic
+gen-lisp: leim semantic unidata
 
 leim:
 	$(MAKE) -C ../leim all EMACS="$(EMACS)"
@@ -357,6 +357,9 @@ leim:
 semantic:
 	$(MAKE) -C ../admin/grammars all EMACS="$(EMACS:.%=../.%)"
 
+unidata:
+	$(MAKE) -C ../admin/unidata all EMACS="$(EMACS:.%=../.%)"
+
 # Compile all Lisp files, but don't recompile those that are up to
 # date.  Some .el files don't get compiled because they set the
 # local variable no-byte-compile.






  parent reply	other threads:[~2017-04-15  1:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  8:54 bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Eli Zaretskii
2017-04-12 15:58 ` Glenn Morris
2017-04-12 16:03   ` Eli Zaretskii
2017-04-12 16:43     ` Glenn Morris
2017-04-12 18:09       ` Glenn Morris
2017-04-13  7:06       ` Eli Zaretskii
2017-04-13  9:03         ` Ken Raeburn
2017-04-13 22:44         ` Paul Eggert
2017-04-14  1:08           ` Glenn Morris
2017-04-14  7:21             ` Eli Zaretskii
2017-04-14 17:08               ` Glenn Morris
2017-04-15  1:25             ` Glenn Morris [this message]
2017-04-15  7:30               ` Eli Zaretskii
2017-04-26 18:32                 ` Glenn Morris
2017-04-26 20:24                   ` Paul Eggert
2017-04-26 20:37                     ` bug#26459: 26.0.50; loaddefs.el is regenerated after each 'git pull' Phillip Lord
2017-04-26 20:47                     ` bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Glenn Morris
2017-04-12 21:37 ` Paul Eggert
2017-04-13  7: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=5ak26mpilr.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=26459@debbugs.gnu.org \
    --cc=eggert@cs.ucla.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).