In file included from /var/tmp/portage/x11-apps/bdftopcf-1.1/work/bdftopcf-1.1/stubs.h:2:0, from /var/tmp/portage/x11-apps/bdftopcf-1.1/work/bdftopcf-1.1/atom.c:37: /var/tmp/portage/x11-apps/bdftopcf-1.1/work/bdftopcf-1.1/fntfilst.h:38:34: fatal error: X11/fonts/fontstruct.h: No such file or directory #include <X11/fonts/fontstruct.h> ^ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma_libressl_20171106-195719 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv x11-apps/bdftopcf [ebuild N ] x11-apps/bdftopcf-1.1
Created attachment 503280 [details] emerge-info.txt
Created attachment 503282 [details] emerge-history.txt
Created attachment 503284 [details] environment
Created attachment 503286 [details] etc.portage.tbz2
Created attachment 503288 [details] logs.tbz2
Created attachment 503290 [details] temp.tbz2
Created attachment 503292 [details] x11-apps:bdftopcf-1.1:20171109-005418.log
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=76529e54aa94be17e866dfcce0a2c63558e95a04 commit 76529e54aa94be17e866dfcce0a2c63558e95a04 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2017-11-11 00:29:47 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2017-11-11 00:29:47 +0000 x11-apps/bdftopcf: Add dependency on x11-proto/fontsproto Closes: https://bugs.gentoo.org/636984 Package-Manager: Portage-2.3.8, Repoman-2.3.3 x11-apps/bdftopcf/bdftopcf-1.1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 636966 has been marked as a duplicate of this bug. ***