Loading /var/tmp/portage/app-editors/xemacs-21.5.34-r4/work/xemacs-21.5.34/lisp/newcomment.elc... Loading /var/tmp/portage/app-editors/xemacs-21.5.34-r4/work/xemacs-21.5.34/lisp/keydefs.elc...make[1]: *** [GNUmakefile:155: xemacs.dmp] Segmentation fault make[1]: Leaving directory '/var/tmp/portage/app-editors/xemacs-21.5.34-r4/work/xemacs-21.5.34/src' make: *** [GNUmakefile:97: src] Error 2 * ERROR: app-editors/xemacs-21.5.34-r4::gentoo failed (compile phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-libressl-20191227-172117 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.40.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sat, 28 Dec 2019 21:47:45 +0000 emerge -qpvO app-editors/xemacs [ebuild N ] app-editors/xemacs-21.5.34-r4 USE="X alsa berkdb gdbm gif gpm jpeg ldap libressl png postgres tiff xft -Xaw3d -athena -canna -debug -dnd -eolconv -freewnn -motif -mule -nas -neXt -pop -xface -xim"
Created attachment 601602 [details] emerge-info.txt
Created attachment 601604 [details] app-editors:xemacs-21.5.34-r4:20191228-223718.log
Created attachment 601606 [details] emerge-history.txt
Created attachment 601608 [details] environment
Created attachment 601610 [details] etc.portage.tbz2
Created attachment 601612 [details] logs.tbz2
Created attachment 601614 [details] temp.tbz2
I'm afraid that I can not recreate this problem. It is similar to the set of bug reports about segmentation faults during the dump phase for xemacs-21.5.34 that has been reported before and is in the bug tracker. None of these I can reproduce. Upstream knows about this problem but there is no solution yet that I know of. I will take the opportunity to check the status with upstream in order to see if there has been any progress in getting a new beta release out that might fix this.
Closing this as a wontfix with reference to that upstream latest master is now available in the 21.5.35 ebuild. Upstream thinks the segmentation violation issues should not be present there.
