When trying to compile grub-9999 with media-fonts/unifont-1.0-r4 (default, as the media-fonts/unifont-5.1* is in testing (keyworded)) it fails due to an empty ascii.bitmaps file, which is due to grub-mkfont not being able to do its job because the glyph-count in the unifont file is too small... yeah I've seen it all ;) Reproducible: Always Steps to Reproduce: 1.install unifont with regular version v1 2.USE=truetype emerge -vt grub-9999 3.
... this actually changed from grub-1.98 + ... you will need grub-9999 to handle imsm fakerads (with a metadata version of >=1.xx)
side-question: Why is the unifont package testing? Could this be lifted to make the 5.1 version the default (there seems on the website of unifont news about an upcoming v5.2)
Please attach the build log. Thank you.
Created attachment 243625 [details] broken build log This line 2 above the failed x86_64-pc-linux-gnu-gcc call are causing the problem: ./grub-mkfont --ascii-bitmaps -o ascii.bitmaps /usr/share/fonts/unifont/unifont.pcf.gz Because it creates an empty ascii.bitmaps file without any (error) message :( The next line then creates the variable ascii_bitmaps in ascii.h: ./grub-bin2h ascii_bitmaps < ascii.bitmaps > ascii.h So that the compile of font/font.c failes, because the variable "ascii_bitmaps" is not set.
added to the tree ... thanks http://sources.gentoo.org/sys-boot/grub/grub-9999.ebuild?r1=1.23&r2=1.24