app-emulation/vice uses the mkfontdir tool as part of the installation process,
but the ebuild doesn't depend on it. So, if mkfontdir isn't already installed
when vice is emerged, the emerge will fail like this:
--- 8< ---
(...)
/bin/install -c -m 644 vice-cbm.bdf
/var/tmp/portage/vice-1.20/image//usr/games/lib/vice/fonts/vice-cbm.bdf
Preparing fontdir...
/bin/sh: line 2: bdftopcf: command not found
/bin/sh: line 4: mkfontdir: command not found
make[2]: *** [install] Error 127
make[2]: Leaving directory
`/var/tmp/portage/vice-1.20/work/vice-1.20/data/fonts'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/vice-1.20/work/vice-1.20/data'
make: *** [install-recursive] Error 1
!!! ERROR: app-emulation/vice-1.20 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_install
ebuild.sh, line 1020: Called src_install
vice-1.20.ebuild, line 79: Called die
!!! emake install failed
!!! If you need support, post the topmost build error, and the call stack if
relevant.
--- 8< ---
Manually installing x11-apps/mkfontdir and emerging vice again makes it work.
So, all that has to be done to fix this bug is to make the vice ebuild depend
on mkfontdir.
Preparing fontdir...
/bin/sh: line 2: bdftopcf: command not found
/bin/sh: line 4: mkfontdir: command not found
make[2]: *** [install] Error 127
make[2]: Leaving directory
`/var/tmp/portage/vice-1.17/work/vice-1.17/data/fonts'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/vice-1.17/work/vice-1.17/data'
make: *** [install-recursive] Error 1
!!! ERROR: app-emulation/vice-1.17 failed.
looks like it isn't fixed in any stable version, this affects x86 and ppc as
far as I can tell.