Loading bytecomp... Loading cl-macs... Loading byte-optimize...make[1]: *** [GNUmakefile:157: update-elc-2] Segmentation fault make[1]: Leaving directory /var/tmp/portage/app-editors/xemacs-21.5.34-r5/work/xemacs-21.5.34/src make: *** [GNUmakefile:76: check-features] Error 2 * ERROR: app-editors/xemacs-21.5.34-r5::gentoo failed (install phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-20200518-061503 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.43.1 * The following VMs are available for generation-2: *) IcedTea JDK 3.16.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed 20 May 2020 04:05:35 PM UTC emerge -qpvO app-editors/xemacs [ebuild N ] app-editors/xemacs-21.5.34-r5 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 640578 [details] emerge-info.txt
Created attachment 640580 [details] app-editors:xemacs-21.5.34-r5:20200520-170142.log
Created attachment 640582 [details] emerge-history.txt
Created attachment 640584 [details] environment
Created attachment 640586 [details] etc.portage.tbz2
Created attachment 640588 [details] logs.tbz2
Created attachment 640590 [details] temp.tbz2
This is in practice as duplicate of https://bugs.gentoo.org/398319. Since the error looks the same and the ebuilds are practically identical. It is also very likely related to the other segmentation violation build errors that has been reported. Upstream has some ideas on what might cause this but have not got around to try it out yet. I have not been able to reproduce this errors this time either as I have not been able to do that for the earlier bug reports related to segmentation violations during xemacs build. Is it OK if I close this as a duplicate even though it is not the same ebuild?
(In reply to Mats Lidell from comment #8) > Is it OK if I close this as a duplicate even though it is not the same > ebuild? sure *** This bug has been marked as a duplicate of bug 398319 ***
*** This bug has been marked as a duplicate of bug 671848 ***
Sorry. My bad. Pasted in the wrong bug. This is the duplicate. https://bugs.gentoo.org/671848
