Hi there! I've found that after some of the updates my portage refuse to install new glibc binpkg on some hosts (while it previously installed it fine on some another, but now it refuses too (so, I can't fully catch the source of that portage behaviour)). When I type: > emerge -Ok glibc I see: > [binary R ] sys-libs/glibc-2.19-r1:2.2 USE="gd* nscd* -debug (-hardened) (-multilib) -profile (-selinux) -suid -systemtap -vanilla" 0 KiB > > Total: 1 package (1 reinstall, 1 binary), Size of downloads: 0 KiB > > > >>> Emerging binary (1 of 1) sys-libs/glibc-2.19-r1::gentoo > * glibc-2.19-r1.tbz2 MD5 SHA1 size ;-) ... [ ok ] > >>> Extracting info > > >>> Failed to emerge sys-libs/glibc-2.19-r1, Log file: > > >>> '/var/log/portage/build/sys-libs/glibc-2.19-r1:20140928-144132.log' > * > * The following package has failed to build or install: > * > * (sys-libs/glibc-2.19-r1:2.2/2.2::gentoo, binary scheduled for merge), Log file: > * '/var/log/portage/build/sys-libs/glibc-2.19-r1:20140928-144132.log' > * > emerge -Ok glibc 5,37s user 0,98s system 58% cpu 10,890 total But log, actually, is even less informative: > >>> Extracting info > * Package: sys-libs/glibc-2.19-r1 > * Repository: gentoo > * USE: x86 abi_x86_32 kernel_linux gd elibc_glibc nscd userland_GNU > * FEATURES: ccache preserve-libs sandbox userpriv usersandbox (that's all). Although, I just found that in emails from portage (custom elog, see emerge info): > Call stack: > ebuild.sh, line 93: Called pkg_setup > environment, line 2868: Called eblit-run 'pkg_setup' > environment, line 985: Called eblit-glibc-pkg_setup > environment, line 841: Called glibc_run_test '#include <pwd.h> > int main(){return getpwuid(0)==0;} > ' > environment, line 2083: Called glibc_compile_test '' '#include <pwd.h> > int main(){return getpwuid(0)==0;} > ' > environment, line 1996: Called nonfatal 'emake' '-s' 'glibc-test' > isolated-functions.sh, line 92: Called die > The specific snippet of code: > die "$FUNCNAME() not supported in this EAPI" > > If you need support, post the output of `emerge --info '=sys-libs/glibc-2.19-r1::gentoo'`, > the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.19-r1::gentoo'`. > The complete build log is located at '/var/log/portage/build/sys-libs/glibc-2.19-r1:20140928-195608.log'. > For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log'. > The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/environment'. > Working directory: '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp' > S: '/var/tmp/portage/sys-libs/glibc-2.19-r1/work/glibc-2.19' Dunno, why portage doesn't notic me on that log saved file...
I am hitting the same problem, and the relevant part is: >> nonfatal() not supported in this EAPI I see that it is tested for and set in: glibc/files/eblits/common.eblit however the nonfatal() is not making it into the bin package's environment. I've tried on both bash types (Shellshocked and non patched) # emerge -Kuav =glibc-2.19-r1 ERROR: setup ERROR: sys-libs/glibc-2.19-r1::gentoo failed (setup phase): nonfatal() not supported in this EAPI Call stack: ebuild.sh, line 93: Called pkg_setup environment, line 2822: Called eblit-run 'pkg_setup' environment, line 939: Called eblit-glibc-pkg_setup environment, line 795: Called glibc_run_test '#include <pwd.h> int main(){return getpwuid(0)==0;} ' environment, line 2037: Called glibc_compile_test '' '#include <pwd.h> int main(){return getpwuid(0)==0;} ' environment, line 1950: Called nonfatal 'emake' '-s' 'glibc-test' isolated-functions.sh, line 94: Called die The specific snippet of code: die "$FUNCNAME() not supported in this EAPI" If you need support, post the output of `emerge --info '=sys-libs/glibc-2.19-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.19-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/environment'. Working directory: '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp' S: '/var/tmp/portage/sys-libs/glibc-2.19-r1/work/glibc-2.19'
Actually, that bugs is bzilla bug because of brokn perl when I reported. Both of they are duplicates of bug #524038 Which, in it's way, semiduplicat of bug #523332 which is caused by "fix" for bug #522962 *** This bug has been marked as a duplicate of bug 524038 ***
