Created attachment 466122 [details] config.log ./configure --prefix=/usr --build=alpha-unknown-linux-gnu --host=alpha-unknown-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --docdir=/usr/share/doc/pam_p11-0.1.5-r2 --htmldir=/usr/share/doc/pam_p11-0.1.5-r2/html --libdir=/usr/lib --disable-static --enable-fast-install checking build system type... alpha-unknown-linux-gnu checking host system type... alpha-unknown-linux-gnu checking target system type... alpha-unknown-linux-gnu checking for a BSD-compatible install... /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for alpha-unknown-linux-gnu-gcc... alpha-unknown-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-auth/pam_p11-0.1.5-r2/work/pam_p11-0.1.5/config.log I've toyed around with it and it seems the added LDFLAGS are the cause. Removing them makes the configure phase pass and the thing compiles (I have done no further testing). Naturally, we'd be back with bug #274924 then (though I don't know if that is still an actual problem). The LDFLAGS of this chroot are the default: LDFLAGS="-Wl,-O1 -Wl,--as-needed"
Strange, I guess it also fail in -r1 as I only changed eapi :) Fixed it properly, I hope. Please check.
