Noticed on MIPS. pam installed with ABI_MIPS=n32. Attempting to build util-linux with ABI_MIPS=n64 results in a linking failure after failing to link with -lpam -lpam_misc. diff --git a/sys-apps/util-linux/util-linux-2.32.ebuild b/sys-apps/util-linux/util-linux-2.32.ebuild index a6b7310e742c..d0cffb6dcf3c 100644 --- a/sys-apps/util-linux/util-linux-2.32.ebuild +++ b/sys-apps/util-linux/util-linux-2.32.ebuild @@ -32,7 +32,7 @@ IUSE="build caps +cramfs fdformat kill ncurses nls pam python +readline selinux RDEPEND="caps? ( sys-libs/libcap-ng ) cramfs? ( sys-libs/zlib:= ) ncurses? ( >=sys-libs/ncurses-5.2-r2:0=[unicode?] ) - pam? ( sys-libs/pam ) + pam? ( sys-libs/pam[${MULTILIB_USEDEP}] ) python? ( ${PYTHON_DEPS} ) readline? ( sys-libs/readline:0= ) selinux? ( >=sys-libs/libselinux-2.2.2-r4[${MULTILIB_USEDEP}] )
This patch would be wrong, since only 1 executable installed only for native ABI uses PAM libraries: # scanelf -qyF "%F: %n" $(qlist sys-apps/util-linux | sort) | grep libpam /sbin/runuser: libpam.so.0,libpam_misc.so.0,libutil.so.1,libc.so.6 # Could you attach full build log and config.log?
Yeah, I think you're right. I was in the process of switching ABIs, and pam wasn't available for the default ABI. I suppose that's not really a case portage is able to handle. Marking as INVALID.
