Summary: | app-editors/xemacs-21.5.34-r4 : make[1]: *** [GNUmakefile:141: update-elc-2] Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | XEmacs team <xemacs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-editors:xemacs-21.5.34-r4:20160612-144550.log
emerge-history.txt environment |
Description
Toralf Förster
![]() Created attachment 437262 [details]
app-editors:xemacs-21.5.34-r4:20160612-144550.log
Created attachment 437264 [details]
emerge-history.txt
Created attachment 437266 [details]
environment
FWIW it builds fine at 3 tinderbox images but failed here : $ for i in amd64-*; do echo $i; qlop -u -l -H -g -f $i/var/log/emerge.log xemacs; done amd64-13.0-unstable_20160605-224630 Sun Jun 12 15:45:38 2016 >>> app-editors/xemacs-21.5.34-r4 xemacs: Sun Jun 12 15:42:26 2016: 3 minutes, 12 seconds xemacs: 1 times amd64-desktop-unstable_20160606-195100 Sun Jun 12 15:21:50 2016 >>> app-editors/xemacs-21.5.34-r4 xemacs: Sun Jun 12 15:17:47 2016: 4 minutes, 3 seconds xemacs: 1 times amd64-gnome-unstable_20160608-203042 amd64-hardened-no-multilib-unstable_20160605-224704 amd64-hardened-unstable_20160605-224713 amd64-plasma-unstable_20160606-203805 Sun Jun 12 16:36:11 2016 >>> app-editors/xemacs-21.5.34-r4 xemacs: Sun Jun 12 16:32:00 2016: 4 minutes, 11 seconds xemacs: 1 times FWIW - at the same tinderbox image the -r3 version did not crash - see bug #585704 (In reply to Toralf Förster from comment #5) > FWIW - at the same tinderbox image the -r3 version did not crash - see bug > #585704 I don't understand. The -r3 version does not even compile with gcc5. The -r4 ebuild with gcc5 patch has been in place for 8 months. The reason it fails now, after being successful, must be due to some other reason but what? (In reply to Mats Lidell from comment #6) Well, this is a hardened host, but I do not found anything in grsec.log nor in pax.log which would point to the hardened features. FWIW it failed today at the freshly setup image amd64-hardened-unstable_20160629-224721 too - so it is reliable. This is solved in the updated xemacs-21.5.34-r4.ebuild which uses the system-malloc in favor for the old XEmacs supplied malloc and -nopie to handle that XEmacs can't yet be built with PIE. |