Re: Build failure for Emacs master

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: Eli Zaretskii <address@hidden>,  address@hidden,  address@hidden
> Date: Wed, 20 Apr 2016 09:18:47 +0100
> 
> Paul Eggert <address@hidden> writes:
> 
> > On 04/18/2016 01:05 PM, Phillip Lord wrote:
> >> The one you fixed on Emacs-25---corruption at the end of loaddefs.
> >
> > I just now merged emacs-25 into master, so the problem should be fixed in
> > master too now.
> 
> 
> Unfortunately, I am still getting failing builds on master, so I guess
> that there is a separate issue. It occurs repeatably, especially on
> parallel builds.
> 
> The end of the build looks like this:
> 
> 
>  ELC      emacs-lisp/autoload.elc
> make[2]: Leaving directory '/d/home/msys-emacs/git/master-copy/lisp'
> make -C ../lisp autoloads EMACS="../src/bootstrap-emacs.exe"
> make[2]: Entering directory '/d/home/msys-emacs/git/master-copy/lisp'
>   GEN      calendar/cal-loaddefs.el
>   GEN      calendar/diary-loaddefs.el
>   GEN      calendar/hol-loaddefs.el
>   GEN      mh-e/mh-loaddefs.el
>   GEN      net/tramp-loaddefs.el
> Directories for loaddefs: . ./calc ./calendar ./cedet ./cedet/ede 
> ./cedet/semantic ./cedet/semantic/analyze ./cedet/semantic/bovine 
> ./cedet/semantic/decorate ./cedet/semantic/symref ./cedet/semantic/wisent 
> ./cedet/srecode ./emacs-lisp ./emulation ./erc ./eshell ./gnus 
> ./international ./language ./leim ./leim/ja-dic ./leim/quail ./mail ./mh-e 
> ./net ./nxml ./org ./play ./progmodes ./textmodes ./url ./vc
>   GEN      loaddefs.el
> Making generated-autoload-file local to  *autoload-file* while let-bound!
> Loading macroexp.elc...
> leim/ja-dic/ja-dic.el:0:0: error: scan-error: (Unbalanced parentheses 413482 
> 2336649)
> Makefile:181: recipe for target 'loaddefs.el' failed

Is this a full bootstrap, or just a rebuild after "git pull"?  If the
latter, copy ldefs-boot.el over loaddefs.el, and try again, or make a
full bootstrap.  (The problem might be triggered by a bad loaddefs.el
left from an old build, before the bug was solved.)