Wrote /var/tmp/portage/app-xemacs/ebuild-mode-1.46/work/ebuild-mode-1.46/gentoo-newsitem-mode.elc Done /var/tmp/portage/app-xemacs/ebuild-mode-1.46/temp/environment: line 565: 30400 Segmentation fault ${XEMACS_BATCH_CLEAN} -eval "(setq autoload-package-name \"${PN}\")" -eval "(setq generated-autoload-file \"${S}/auto-autoloads.el\")" -l autoload -f batch-update-autoloads "$@" * ERROR: app-xemacs/ebuild-mode-1.46::gentoo failed (compile phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20181127-210345 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby24 (with Rubygems) [3] ruby25 (with Rubygems) * emerge -qpvO app-xemacs/ebuild-mode [ebuild N ] app-xemacs/ebuild-mode-1.46
Created attachment 556686 [details] emerge-info.txt
Created attachment 556688 [details] app-xemacs:ebuild-mode-1.46:20181129-001323.log
Created attachment 556690 [details] emerge-history.txt
Created attachment 556692 [details] environment
Created attachment 556694 [details] etc.portage.tbz2
Created attachment 556696 [details] temp.tbz2
I can't reproduce this on my machine. It would be interesting to run a debug build on that machine and create a backtrace of the error. Would that be possible? That could give upstream valuable info about the error.
(In reply to Mats Lidell from comment #7) If you can put here the steps to be made I could try to code that into the tinderbox
I cannot reproduce this either. Is this still an issue with ebuild-mode-1.55?
(In reply to Ulrich Müller from comment #9) > I cannot reproduce this either. Is this still an issue with ebuild-mode-1.55? no
