-l finder -f finder-compile-keywords Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)make[1]: *** [GNUmakefile:161: /var/tmp/portage/app-editors/xemacs-21.5.34-r4/work/xemacs-21.5.34/src/../lisp/finder-inf.el] 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.0-developer_abi32+64_20180715-201646 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.8.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-editors/xemacs [nomerge ] app-editors/xemacs-21.5.34-r4 USE="X alsa berkdb gdbm gif gpm jpeg ldap png tiff -Xaw3d -athena -canna -debug -dnd -eolconv -freewnn -libressl -motif -mule -nas -neXt -pop -postgres -xface -xft -xim" [ebuild N ] app-xemacs/xemacs-base-2.27 [ebuild N ] app-editors/xemacs-21.5.34-r4 USE="X alsa berkdb gdbm gif gpm jpeg ldap png tiff -Xaw3d -athena -canna -debug -dnd -eolconv -freewnn -libressl -motif -mule -nas -neXt -pop -postgres -xface -xft -xim"
Created attachment 540096 [details] emerge-info.txt
Created attachment 540098 [details] app-editors:xemacs-21.5.34-r4:20180719-080233.log
Created attachment 540100 [details] emerge-history.txt
Created attachment 540102 [details] environment
Created attachment 540104 [details] etc.portage.tbz2
Created attachment 540106 [details] logs.tbz2
Created attachment 540108 [details] temp.tbz2
I can confirm the error. I got this error once after doing some initial builds when looking at this bug report. After that I have tried multiple times to recreate the error in order to find a stable way of getting the problem to show up but I have failed in doing so. The build has not failed a single time after that. So now I it seems I can't recreate it. I will check with upstream what they make of this.
Asked about the issue in the upstream forum. https://list-archive.xemacs.org/archive/list/xemacs-beta@xemacs.org/message/YDQV7W7KC3Y6KUSRDNJFXOJJRXWFPPGX/
app-editors/xemacs-21.5.34-r9 has been updated with back ported changes from upstream tip version that addresses this error. Closing this as resolved.
