[debbugs-tracker] bug#35409: closed (27.0.50; Emacs master can't be built in Win 10)

[GNU bug Tracking System]

Your message dated Wed, 01 May 2019 19:58:03 +0300
with message-id <address@hidden>
and subject line Re: bug#35409: 27.0.50; Emacs master can't be built in Win 10
has caused the debbugs.gnu.org bug report #35409,
regarding 27.0.50; Emacs master can't be built in Win 10
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
35409: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35409
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 27.0.50; Emacs master can't be built in Win 10
>
>
>
>
> Date: 
>
> Wed, 24 Apr 2019 13:55:42 +0800
>
>
>
>
> Hi all,
>
> I tried to build emacs master from 22 April till
> 5f4e8e2e088de9fb76cb631077c6eddd3219f594. 
> It fails with following message:
>
> --8<---------------cut here---------------start------------->8---
> Loading c:/gitemacs/emacs/lisp/emacs-lisp/lisp.el (source)...
> Loading c:/gitemacs/emacs/lisp/textmodes/page.el (source)...
> Loading c:/gitemacs/emacs/lisp/register.el (source)...
> Loading c:/gitemacs/emacs/lisp/textmodes/paragraphs.el (source)...
> Loading c:/gitemacs/emacs/lisp/progmodes/prog-mode.el (source)...
> Loading c:/gitemacs/emacs/lisp/emacs-lisp/lisp-mode.el (source)...
> Loading c:/gitemacs/emacs/lisp/progmodes/elisp-mode.el (source)...
> make[1]: *** [Makefile:808: bootstrap-emacs.pdmp] Segmentation fault
> make[1]: Leaving directory '/c/gitemacs/emacs/src'
> make: *** [Makefile:423: src] Error 2
> --8<---------------cut here---------------end--------------->8---
>
>
>
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#35409: 27.0.50; Emacs master can't be built in Win 10
>
>
>
>
> Date: 
>
> Wed, 01 May 2019 19:58:03 +0300
>
>
>
>
> > From: Shuguang Sun <address@hidden>
> > Cc: address@hidden
> > Date: Wed, 01 May 2019 15:01:18 +0800
> > 
> > The new response version can be successfully compiled now.
>
> Thanks, I'm therefore closing the bug report.
>
>
> --- End Message ---