All of the ebuilds are using EAPI 7, but none defines BDEPEND. They put xz and portage-utils in DEPEND, which causes them to be cross-compiled. It looks like portage-utils is for executing qatom natively, and I don't see xz being used anywhere (unless you run "make dist", but the ebuild won't do that). Please move portage-utils to BDEPEND so it doesn't needlessly cross-compile package management stuff to install some config files, and drop xz if it is unused. Reproducible: Always Steps to Reproduce: 1. emerge -v sys-auth/pambase # with a sysroot profile Actual Results: It cross-compiles portage-utils. Expected Results: It should natively install portage-utils so it can execute qatom. Unrelatedly, the (unused?) LINUX_PAM_VERSION definition can't handle pam snapshot version numbers, but it still seems to output the correct version string: /var/tmp/portage/sys-auth/pambase-20190402/temp/environment: line 1062: printf: 1_p20200128: invalid number Anyway, this works for me: --- sys-auth/pambase/pambase-20190402.ebuild +++ sys-auth/pambase/pambase-20190402.ebuild @@ -36,8 +36,7 @@ sha512? ( >=sys-libs/pam-${MIN_PAM_REQ} ) systemd? ( sys-apps/systemd[pam] ) " -DEPEND=" - app-arch/xz-utils +BDEPEND=" app-portage/portage-utils "
We do not force people to switch to BDEPEND yet. v20200804 has been completely rewritten and is not using portage-utils anymore (you can switch to this version as well, I am happy with testing). I do not see the point to touch already working ebuilds.
