Created attachment 401902 [details] build.log >>> Emerging (1 of 1) dev-libs/glib-2.40.2::gentoo openpty failed: 'out of pty devices' * glib-2.40.2.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * pkg-config-0.28.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.18.9-hardened * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Unpacking glib-2.40.2.tar.xz to /var/tmp/portage/dev-libs/glib-2.40.2/work >>> Unpacking pkg-config-0.28.tar.gz to /var/tmp/portage/dev-libs/glib-2.40.2/work >>> Source unpacked in /var/tmp/portage/dev-libs/glib-2.40.2/work >>> Preparing source in /var/tmp/portage/dev-libs/glib-2.40.2/work/glib-2.40.2 ... mv: cannot stat '/var/tmp/portage/dev-libs/glib-2.40.2/work/pkg-config-*/pkg.m4': No such file or directory * ERROR: dev-libs/glib-2.40.2::gentoo failed (prepare phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 5934: Called die * The specific snippet of code: * mv -f "${WORKDIR}"/pkg-config-*/pkg.m4 "${S}"/m4macros/ || die; * * If you need support, post the output of `emerge --info '=dev-libs/glib-2.40.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/glib-2.40.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-libs/glib-2.40.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.40.2/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/glib-2.40.2/work/glib-2.40.2' * S: '/var/tmp/portage/dev-libs/glib-2.40.2/work/glib-2.40.2'
Created attachment 401904 [details] emerge info
Created attachment 401906 [details] emerge -pqv
What output do you get when running sudo ls -l /var/tmp/portage/dev-libs/glib-2.40.2/work sudo ls /var/tmp/portage/dev-libs/glib-2.40.2/work/pkg-config-0.28/pkg.m4 after a build failure?
Created attachment 402082 [details] munin file into folder
Done
Duplicate of bug 518598 ?
hard to say
I'm pretty sure it's the same bug.
Most likely a duplicate indeed. *** This bug has been marked as a duplicate of bug 518598 ***