Please keyword GRUB for use on RISC-V systems. I've been using it for about a year with no issues.
Sanity check failed: > sys-boot/grub-2.06_rc1 > depend ~riscv stable profile default/linux/riscv/17.0/rv64gc/lp64 (4 total) > media-libs/libsdl > rdepend ~riscv stable profile default/linux/riscv/17.0/rv64gc/lp64 (4 total) > media-libs/libsdl > sys-boot/efibootmgr
Do libsdl and efibootmgr work for you as well?
I haven't tried SDL with it, since it is only a dependency when GRUB_PLATFORMS="emu" is used. It all builds successfully, though. I am using UEFI, but I forgot my setup was skipping efibootmgr. I built it before, but it had to use live ebuilds, and there are a couple pending failures upstream that I don't recall now (like https://github.com/rhboot/efivar/pull/169 ). Another thing about my environment that should probably be addressed: GRUB must set BUILD_PKG_CONFIG=pkg-config in the environment to cross-compile with USE=themes. (Maybe add it to the "tc-export BUILD_CC" line.) Sorry if keywording this isn't possible due to efibootmgr. I opened this request since I was accepting testing GRUB ebuilds everywhere due to needing recent fixes, and I'd like to drop that since the RC is being stabilized, but that would leave riscv behind. I can just keep accepting specific GRUB ebuilds for riscv if that's a blocker. (Or I can go back to pestering all the EFI-related upstream packages to supporting RISC-V properly, but that will take a long time if not forever.)
A message on grub-devel just reminded me of another point: the Linux loader patches aren't applied upstream yet. GRUB can still boot UEFI kernels with the "chainloader" command, but the "linux" command says it's not supported, in case that is a requirement for keywording.
An alternative would be to package.use.mask the sdl USE flag on riscv, and move the efibootmgr dependency behind a "!riscv ( )" condition. However, since there is still a bit of work happening on this upstream, I think I would prefer not to keyword this on riscv at the moment.
