>>> Install app-emacs/mailcrypt-3.5.9-r1 into /var/tmp/portage/app-emacs/mailcrypt-3.5.9-r1/image make -j1 lispdir=/var/tmp/portage/app-emacs/mailcrypt-3.5.9-r1/image/usr/share/emacs/site-lisp/mailcrypt infodir=/var/tmp/portage/app-emacs/mailcrypt-3.5.9-r1/image/usr/share/info install make: *** No rule to make target 'FSF-timer.el', needed by 'timer.el'. Stop. * ERROR: app-emacs/mailcrypt-3.5.9-r1::gentoo failed (install phase): * emake failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-libressl-20191012-161543 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.0 (tags/RELEASE_900/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.0 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.38.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Thu, 17 Oct 2019 05:46:05 +0000 emerge -qpvO app-emacs/mailcrypt [ebuild N ] app-emacs/mailcrypt-3.5.9-r1
Created attachment 593024 [details] emerge-info.txt
Created attachment 593026 [details] app-emacs:mailcrypt-3.5.9-r1:20191017-085325.log
Created attachment 593028 [details] emerge-history.txt
Created attachment 593030 [details] environment
Created attachment 593032 [details] etc.portage.tbz2
Created attachment 593034 [details] logs.tbz2
Created attachment 593036 [details] temp.tbz2
(In reply to Toralf Förster from comment #2) > Created attachment 593026 [details] > app-emacs:mailcrypt-3.5.9-r1:20191017-085325.log Looks like the problem is in configure: > checking for timer.el...no. I will install it for you. This is strange, because emacs-26.3 should definitely install timer.el (and timer.elc) in /usr/share/emacs/26.3/lisp/emacs-lisp/. What does the following command output, and what exit status does it return? $ /usr/bin/emacs -batch -l timer In case it returns a non-zero status, is the following any different? $ /usr/bin/emacs -batch -q --no-site-file -l timer
(In reply to Ulrich Müller from comment #8) Anyway, this should be fixed in -r3, which bypasses the quirky upstream build system entirely, and uses the functions from elisp.eclass instead.
(In reply to Ulrich Müller from comment #8) > $ /usr/bin/emacs -batch -l timer > > In case it returns a non-zero status, is the following any different? > > $ /usr/bin/emacs -batch -q --no-site-file -l timer tinderbox@mr-fox ~ $ chr img1/17.1_no-multilib-libressl-20191012-161543 mr-fox ~ # /usr/bin/emacs -batch -l timer Cannot open load file: No such file or directory, matlab-load mr-fox ~ # /usr/bin/emacs -batch -q --no-site-file -l timer mr-fox ~ # exit logout
Presumably, this is due to a missing autoload file in app-emacs/matlab-3.3.2_pre20130829. Closing as duplicate of bug 698006. *** This bug has been marked as a duplicate of bug 698006 ***