>>> Messages generated by process 9066 on 2017-09-12 10:47:28 CEST for package dev-libs/libmowgli-1.0.0: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 9066 on 2017-09-12 10:47:43 CEST for package media-libs/faad2-2.7-r3: QA: prepare This package has a configure.in file which has long been deprecated. Please update it to use configure.ac instead as newer versions of autotools will die when it finds this file. See https://bugs.gentoo.org/426262 for details. >>> Messages generated by process 9066 on 2017-09-12 10:48:10 CEST for package app-i18n/libguess-1.2: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 9066 on 2017-09-12 10:48:22 CEST for package media-libs/adplug-2.2.1: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found QA: other QA Notice: Package triggers severe warnings which indicate that it may exhibit random runtime failures. fmopl.c:601:20: warning: iteration 15u invokes undefined behavior [-Waggressive-loop-optimizations] mid.cpp:873:53: warning: iteration 14u invokes undefined behavior [-Waggressive-loop-optimizations] Please do not file a Gentoo bug and instead report the above QA issues directly to the upstream developers of this software. Homepage: http://adplug.sourceforge.net >>> Messages generated by process 9066 on 2017-09-12 10:48:50 CEST for package media-sound/audacious-3.7.1: QA: install QA Notice: Unrecognized configure options: --enable-chardet --enable-chardet >>> Messages generated by process 9066 on 2017-09-12 10:49:18 CEST for package media-plugins/audacious-plugins-3.7.1: QA: install QA Notice: Unrecognized configure options: --enable-statusicon --enable-adplug --enable-statusicon --enable-adplug >>> Messages generated by process 1365 on 2017-09-12 11:06:01 CEST for package media-video/mpv-0.25.0-r2: LOG: postinst If you want to have command-line completion via bash-completion, please install app-shells/mpv-bash-completion. >>> Messages generated by process 18893 on 2017-09-12 11:19:45 CEST for package app-eselect/eselect-opencl-1.1.0-r1: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 18893 on 2017-09-12 11:21:33 CEST for package virtual/linux-sources-3: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 18893 on 2017-09-12 11:24:15 CEST for package sys-power/acpid-2.0.28: LOG: postinst You may wish to read the Gentoo Linux Power Management Guide, which can be found online at: https://wiki.gentoo.org/wiki/Power_management/Guide WARN: postinst You should reboot the system now to get /run mounted with tmpfs! >>> Messages generated by process 18884 on 2017-09-12 11:24:44 CEST for package sys-devel/llvm-3.9.1-r1: QA: other QA Notice: The following shared libraries lack NEEDED entries /usr/lib32/libLLVMGlobalISel.so.39.1 /usr/lib64/libLLVMGlobalISel.so.39.1 >>> Messages generated by process 18884 on 2017-09-12 11:25:03 CEST for package net-wireless/wpa_supplicant-2.6-r2: LOG: postinst If this is a clean installation of wpa_supplicant, you have to create a configuration file named /etc/wpa_supplicant/wpa_supplicant.conf An example configuration file is available for reference in /usr/share/doc/wpa_supplicant-2.6-r2/ >>> Messages generated by process 18893 on 2017-09-12 11:25:32 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 18884 on 2017-09-12 11:31:00 CEST for package net-analyzer/wireshark-2.2.7: WARN: postinst NOTE: To capture traffic with wireshark as normal user you have to add yourself to the wireshark group. This security measure ensures that only trusted users are allowed to sniff your traffic. >>> Messages generated by process 18884 on 2017-09-12 11:31:53 CEST for package app-editors/emacs-25.2: WARN: configure USE flag "alsa" overrides "-sound"; enabling sound support. Your version of GTK+ will have problems with closing open displays. This is no problem if you just use one display, but if you use more than one and close one of them Emacs may crash. See . If you intend to use more than one display, then it is strongly recommended that you compile Emacs with the Athena/Lucid or the Motif toolkit instead. >>> Messages generated by process 18884 on 2017-09-12 11:32:20 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3800: Called cmake-utils_src_configure environment, line 1238: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 18884 on 2017-09-12 11:32:55 CEST for package app-crypt/pinentry-0.9.7-r1: QA: other QA Notice: Package triggers severe warnings which indicate that it may exhibit random runtime failures. pinentry-curses.c:110:18: warning: implicit declaration of function 'addnwstr' [-Wimplicit-function-declaration] Please do not file a Gentoo bug and instead report the above QA issues directly to the upstream developers of this software. Homepage: http://gnupg.org/aegypten2/index.html >>> Messages generated by process 6620 on 2017-09-12 14:36:37 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: setup These sources have not yet been prepared. We cannot build against an unprepared tree. To resolve this, please type the following: # cd /usr/src/linux # make oldconfig # make modules_prepare Then please try merging this module again. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase): Kernel sources need compiling first Call stack: ebuild.sh, line 115: Called pkg_setup nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup linux-mod.eclass, line 573: Called check_kernel_built linux-info.eclass, line 663: Called die The specific snippet of code: die "Kernel sources need compiling first" If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 10450 on 2017-09-12 14:37:16 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: setup These sources have not yet been prepared. We cannot build against an unprepared tree. To resolve this, please type the following: # cd /usr/src/linux # make oldconfig # make modules_prepare Then please try merging this module again. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase): Kernel sources need compiling first Call stack: ebuild.sh, line 115: Called pkg_setup nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup linux-mod.eclass, line 573: Called check_kernel_built linux-info.eclass, line 663: Called die The specific snippet of code: die "Kernel sources need compiling first" If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 12941 on 2017-09-12 14:40:19 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: setup These sources have not yet been prepared. We cannot build against an unprepared tree. To resolve this, please type the following: # cd /usr/src/linux # make oldconfig # make modules_prepare Then please try merging this module again. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase): Kernel sources need compiling first Call stack: ebuild.sh, line 115: Called pkg_setup nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup linux-mod.eclass, line 573: Called check_kernel_built linux-info.eclass, line 663: Called die The specific snippet of code: die "Kernel sources need compiling first" If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 15380 on 2017-09-12 14:42:50 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: setup These sources have not yet been prepared. We cannot build against an unprepared tree. To resolve this, please type the following: # cd /usr/src/linux # make oldconfig # make modules_prepare Then please try merging this module again. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase): Kernel sources need compiling first Call stack: ebuild.sh, line 115: Called pkg_setup nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup linux-mod.eclass, line 573: Called check_kernel_built linux-info.eclass, line 663: Called die The specific snippet of code: die "Kernel sources need compiling first" If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 17881 on 2017-09-12 14:44:10 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: setup These sources have not yet been prepared. We cannot build against an unprepared tree. To resolve this, please type the following: # cd /usr/src/linux # make oldconfig # make modules_prepare Then please try merging this module again. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (setup phase): Kernel sources need compiling first Call stack: ebuild.sh, line 115: Called pkg_setup nvidia-drivers-384.69.ebuild, line 142: Called linux-mod_pkg_setup linux-mod.eclass, line 573: Called check_kernel_built linux-info.eclass, line 663: Called die The specific snippet of code: die "Kernel sources need compiling first" If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/die.env'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/homedir' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 13864 on 2017-09-12 15:07:03 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 20321 on 2017-09-12 15:09:22 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 26777 on 2017-09-12 15:12:27 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 779 on 2017-09-12 15:14:06 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 7396 on 2017-09-12 15:20:10 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 13876 on 2017-09-12 15:23:32 CEST for package x11-base/xorg-drivers-1.19: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 13876 on 2017-09-12 15:24:25 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 13876 on 2017-09-12 15:27:10 CEST for package media-libs/mesa-17.0.6: ERROR: compile ERROR: media-libs/mesa-17.0.6::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=media-libs/mesa-17.0.6::gentoo'`, the complete build log and the output of `emerge -pqv '=media-libs/mesa-17.0.6::gentoo'`. The complete build log is located at '/var/tmp/portage/media-libs/mesa-17.0.6/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-17.0.6/temp/environment'. Working directory: '/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6-abi_x86_32.x86' S: '/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6' >>> Messages generated by process 924 on 2017-09-12 15:28:31 CEST for package x11-base/xorg-drivers-1.19: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 924 on 2017-09-12 15:34:14 CEST for package media-libs/mesa-17.0.6: LOG: postinst USE="bindist" was not set. Potentially patent encumbered code was enabled. Please see patents.txt for an explanation. Note that in order to have full S3TC support, it is necessary to install media-libs/libtxc_dxtn as well. This may be necessary to get nice textures in some apps, and some others even require this to run. >>> Messages generated by process 924 on 2017-09-12 17:30:14 CEST for package www-client/chromium-61.0.3163.79: ERROR: setup USER_NS is required for sandbox to work CONFIG_COMPAT_VDSO causes segfaults (bug #556286) WARN: setup Please check to make sure these options are set correctly. Failure to do so may cause unexpected problems. >>> Messages generated by process 924 on 2017-09-12 17:30:17 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3787: Called cmake-utils_src_configure environment, line 1225: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 924 on 2017-09-12 17:31:03 CEST for package dev-qt/qtwebkit-5.7.1: ERROR: compile ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' >>> Messages generated by process 924 on 2017-09-12 17:32:31 CEST for package x11-misc/lightdm-1.18.3: QA: other This package seems to install gtk-doc documentation into the following location(s): /usr/share/doc/lightdm-1.18.3/html/lightdm-gobject-1 gtk-doc documentation must always be installed into /usr/share/gtk-doc. For more details, please see the GNOME team policy page: https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies#gtk-doc >>> Messages generated by process 6955 on 2017-09-13 14:35:52 CEST for package www-client/firefox-52.3.0: LOG: setup You are enabling official branding. You may not redistribute this build to any users on your network or the internet. Doing so puts yourself into a legal problem with Mozilla Foundation You can disable it by emerging firefox _with_ the bindist USE-flag >>> Messages generated by process 30989 on 2017-09-13 16:00:05 CEST for package x11-base/xorg-drivers-1.19: QA: install QA Notice: command not found: /etc/portage/bashrc: line 8: epatch_user: command not found >>> Messages generated by process 30989 on 2017-09-13 16:01:01 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 30989 on 2017-09-13 16:06:25 CEST for package media-libs/mesa-17.0.6: LOG: postinst USE="bindist" was not set. Potentially patent encumbered code was enabled. Please see patents.txt for an explanation. Note that in order to have full S3TC support, it is necessary to install media-libs/libtxc_dxtn as well. This may be necessary to get nice textures in some apps, and some others even require this to run. >>> Messages generated by process 30989 on 2017-09-13 16:06:28 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3800: Called cmake-utils_src_configure environment, line 1238: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 30989 on 2017-09-13 16:06:47 CEST for package dev-qt/qtwebkit-5.7.1: ERROR: compile ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' >>> Messages generated by process 10962 on 2017-09-13 16:19:32 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 10962 on 2017-09-13 16:22:58 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3800: Called cmake-utils_src_configure environment, line 1238: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 10962 on 2017-09-13 16:23:17 CEST for package dev-qt/qtwebkit-5.7.1: ERROR: compile ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' >>> Messages generated by process 22721 on 2017-09-13 16:38:06 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 30037 on 2017-09-13 16:54:21 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 6076 on 2017-09-13 16:57:35 CEST for package x11-drivers/nvidia-drivers-384.59-r1: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/' >>> Messages generated by process 6076 on 2017-09-13 16:57:46 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3800: Called cmake-utils_src_configure environment, line 1238: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 6076 on 2017-09-13 16:58:06 CEST for package dev-qt/qtwebkit-5.7.1: ERROR: compile ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' >>> Messages generated by process 7688 on 2017-09-14 14:16:05 CEST for package x11-drivers/nvidia-drivers-384.69: ERROR: compile ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`, the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel' S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/' >>> Messages generated by process 7688 on 2017-09-14 14:16:17 CEST for package app-admin/conky-1.10.4: ERROR: configure ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase): cmake failed Call stack: ebuild.sh, line 115: Called src_configure environment, line 3800: Called cmake-utils_src_configure environment, line 1238: Called die The specific snippet of code: "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`, the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build' S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4' >>> Messages generated by process 7688 on 2017-09-14 14:16:38 CEST for package dev-qt/qtwebkit-5.7.1: ERROR: compile ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase): emake failed If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1' S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'