I recently stumbled upon this issue: * Package: sys-apps/sandbox-2.39:0 * Repository: gentoo * Maintainer: sandbox@gentoo.org * USE: abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux nnp * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * abi_x86_32.x86: running multilib-minimal_abi_src_configure checking for a BSD-compatible install... /usr/lib/portage/python3.12/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking environment state... ok checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32 -mfpmath=sse checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in '/var/tmp/portage/sys-apps/sandbox-2.39/work/sandbox-2.39-abi_x86_32.x86': configure: error: cannot run C compiled programs. config.log says: /var/tmp/portage/sys-apps/sandbox-2.39/work/sandbox-2.39/configure: line 4394: ./conftest: cannot execute binary file: Exec format error this is because I do not have: CONFIG_IA32_EMULATION CONFIG_X86_X32_ABI that should be checked someway (not sure atm if both are needed) Assigning to toolchain@ as maintainer of multilib.eclass, not sure if the fix goes there or elsewhere.
*** This bug has been marked as a duplicate of bug 920217 ***
Note that it's not about kernel modules but kernel configuration. I don't think we should add a pkg_pretend/pkg_setup to every ebuild using multilib*. I also really just consider this obviously invalid configuration. Don't set it unless you are *absolutely sure* you're not going to need it...
(In reply to Sam James from comment #2) > Note that it's not about kernel modules but kernel configuration. > > I don't think we should add a pkg_pretend/pkg_setup to every ebuild using > multilib*. > > I also really just consider this obviously invalid configuration. Don't set > it unless you are *absolutely sure* you're not going to need it... I agree, I just removed it because a mistake. Since other ebuilds behave differently in case they need a kernel configuration/module I though it was good to fix, but it is fine as-is