Created attachment 391602 [details] sys-boot:grub-2.02_beta2-r6:20141213-205502.log emerging sys-boot/grub-2.02_beta2-r6 fails to emerge Section from build log with errors: PATH=.:$PATH pkgdatadir=. /usr/bin/help2man --section=8 -i /var/tmp/portage/sys-boot/grub-2.02_beta2-r6/work/grub-2.02~beta2/docs/man/grub-reboot.h2m -o grub-reboot.8 grub-reboot ./build-grub-mkfont -o unicode.pf2 ./unifont.pcf || (rm -f unicode.pf2; exit 1) can't open file ./unifont.pcf, index 0: error 2: unknown file format ./build-grub-mkfont -o ascii.pf2 ./unifont.pcf -r 0x0-0x7f,0x2190-0x2193,0x2501-0x251B || (rm -f ascii.pf2; exit 1) can't open file ./unifont.pcf, index 0: error 2: unknown file format
Created attachment 391604 [details] emerge --info
I got the same error
The cause for this failure seems to be in the (unstable) media-libs/freetype-2.5.4. Both the 2.02_beta2-r3 and r6 are building fine with (stable) media-libs/freetype-2.5.3-r1
Copying the freetype maintainers. Any idea why freetype would stop recognizing this pcf font?
This has been reported at freetype upstream. Adjusting summary and re-assigning. http://savannah.nongnu.org/bugs/?43774
Thanks for reporting and helping to narrow it down to a freetype problem. +*freetype-2.5.4-r1 (14 Dec 2014) + + 14 Dec 2014; Mike Gilbert <floppym@gentoo.org> + +files/2.5.4-0001-pcf-Fix-Savannah-bug-43774.patch, + +files/2.5.4-0002-src-pcf-pcfread.c-pcf_read_TOC-Improve-fix-from-2014.patch, + +freetype-2.5.4-r1.ebuild, -freetype-2.5.4.ebuild: + Backport fixes for bug 532506.
*** Bug 532592 has been marked as a duplicate of this bug. ***
*** Bug 532706 has been marked as a duplicate of this bug. ***