Some parts of the devkitARM build scripts assume /opt/devkitpro is the installation directory and fail to build if a different path is chosen about buildscripts HOT 5 CLOSED

We don't support use of the tools in custom prefixes nor do we support 3rd party packaging.

from buildscripts.

Can you at least add a note to the README that it requires /opt/devkitpro as the prefix?

from buildscripts.

Can you at least add a note to the README that it requires /opt/devkitpro as the prefix?

c04144a should cover it.

FWIW, devkitPro tooling can be managed on voidLinux with pacman quite happily. See https://devkitpro.org/viewtopic.php?t=8847

from buildscripts.

FWIW, devkitPro tooling can be managed on voidLinux with pacman quite happily

Yeah, you can just follow the steps here:
https://devkitpro.org/wiki/devkitPro_pacman

On glibc, the steps are basically the same as Fedora, just instead of dnf install, use xpbs-install.
On musl, you need to use a glibc chroot: https://docs.voidlinux.org/config/containers-and-vms/chroot.html

from buildscripts.

I installed pacman from the void repos and added the devkitpro repository. Thanks.

from buildscripts.