Hi Adrian,
On 9 Nov 2020, at 14:20, John Paul Adrian Glaubitz wrote:
Hi!
On 10/30/20 10:49 AM, John Paul Adrian Glaubitz wrote:
Just as a heads-up, emacs 27 is failing to build from source on m68k
[1]:
Loading
/<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/vc/ediff-hook.el
(source)...
Loading /<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/uniquify.el
(source)...
Loading /<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/electric.el
(source)...
Loading
/<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/emacs-lisp/eldoc.el
(source)...
Loading
/<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/cus-start.el
(source)...
Loading /<<BUILDDIR>>/emacs-27.1+1/debian/build-src/lisp/tooltip.el
(source)...
Finding pointers to doc strings...
Finding pointers to doc strings...done
Dumping under the name bootstrap-emacs.pdmp
dumping fingerprint:
0a633170371949b7c12d424d042472d5315e0c291484a3bcbabc8d00b5dd75aa
dump relocation out of range
make[3]: *** [Makefile:817: bootstrap-emacs.pdmp] Error 255
make[3]: Leaving directory
'/<<BUILDDIR>>/emacs-27.1+1/debian/build-gtk/src'
make[2]: *** [Makefile:426: src] Error 2
make[2]: Leaving directory
'/<<BUILDDIR>>/emacs-27.1+1/debian/build-gtk'
make[1]: *** [debian/rules:335: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<BUILDDIR>>/emacs-27.1+1'
make: *** [debian/rules:204: build-arch] Error 2
Unless someone has any idea how to fix the issue, I will report the
problem upstream.
The issue reproduces on qemu-m68k-system as well.
You could try "--with-pdumper=no" in the configure step as a workaround.
As I understand, Emacs changed the dumper from "unexec" to "pdumper"
(https://dancol.org/pdumperpres.pdf) in Version 27.1.
From https://www.masteringemacs.org/article/whats-new-in-emacs-27-1
""
Emacs now uses a "portable dumper" instead of unexec.
This improves compatibility with memory allocation on modern systems,
and in particular better supports the Address Space Layout
Randomization (ASLR) feature, a security technique used by most
modern
operating systems.
""
With the above configuration setting, you get the old dumper back. That
is not a long-term solution, but a workaround until the root cause of
the issue with the portable dumper is found.
Greetings
Carsten