Re: Error after dump complete when compile on Windows 10

[Eli Zaretskii]

[This is not the right place to report build problems and crashes,
certainly not in the development version.  Please submit a bug report
with all the details instead, using "M-x report-emacs-bug".]

> From: "Shuguang Sun" <shuguang79@qq.com>
> Date: Fri, 1 Feb 2019 00:23:18 +0800
> Feedback-ID: webmail:qq.com:bgweb:bgweb115
> 
> I'm try to build emacs on Windows 10 using msys2/mingw64, and git emacs 
> source. However, it raises error after dump complete. Does any one compile it 
> successfully on Windows 10?

I see no reason why Windows 10 would be special.

> With configure:
>  PKG_CONFIG_PATH=/mingw64/lib/pkgconfig ./configure --host=x86_64-w64-mingw32 
>  --target=x86_64-w64-mingw32 --build=x86_64-w64-mingw32

Why do you specify host, target, and build explicitly?

Also, when did you last check out from Git?  And what are your GCC and
Binutils versions?

> Dump complete
> Byte counts: header=80 hot=13293288 discardable=127776 cold=9178020
> Reloc counts: hot=920625 discardable=4848
> make -C ../lisp compile-first EMACS="../src/bootstrap-emacs.exe"
> make[2]: Entering directory '/c/Users/username/gitemacs/emacs/lisp'
>   ELC      emacs-lisp/macroexp.elc
>   ELC      emacs-lisp/cconv.elc
>   ELC      emacs-lisp/byte-opt.elc
> /bin/sh: line 1: 195564 Segmentation fault      EMACSLOADPATH= 
> '../src/bootstrap-emacs.exe' -batch --no-site-file --no-site-lisp --eval 
> '(setq load-prefer-newer t)' -f batch-byte-compile emacs-lisp/cconv.el
> make[2]: *** [Makefile:301: emacs-lisp/cconv.elc] Error 139

What happens if you configure with --with-dumping=unexec option, does
it succeed to build then?