xemacs exiting. End of file or stream: "internal input stream" * ERROR: app-xemacs/ebuild-mode-1.55::gentoo failed (compile phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j4-20220121-110042 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): clang version 13.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.58.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] *) Eclipse Temurin JDK 8.312_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm [2] openjdk-bin-11 The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 [3] php8.1 * HEAD of ::gentoo commit 78486293f8f3e978dc6d5b416b75be3af4bf4f1c Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Jan 24 08:37:01 2022 +0000 2022-01-24 08:36:59 UTC emerge -qpvO app-xemacs/ebuild-mode [ebuild N ] app-xemacs/ebuild-mode-1.55
Created attachment 763472 [details] emerge-info.txt
Created attachment 763473 [details] app-xemacs:ebuild-mode-1.55:20220124-092210.log
Created attachment 763474 [details] emerge-history.txt
Created attachment 763475 [details] environment
Created attachment 763476 [details] etc.portage.tar.bz2
Created attachment 763477 [details] temp.tar.bz2
Thanks for the report. I have not been able to recreate the problem. Checking with upstream for ideas.
tinderbox has reproduced this issue with version 1.57 - Updating summary.
Thanks for the update. I can't recreate the problem. Upstream knows about the issue but have no solution since it has not been possible yet(!?) to recreate it.
Is this still an issue with app-xemacs/ebuild-mode-1.66?
(In reply to Ulrich Müller from comment #10) > Is this still an issue with app-xemacs/ebuild-mode-1.66? solved IMO