spacepaste

Paste details

reply | raw

  1.  
  2. >>> Messages generated by process 9066 on 2017-09-12 10:47:28 CEST for package dev-libs/libmowgli-1.0.0:
  4. QA: install
  5. QA Notice: command not found:
  7. /etc/portage/bashrc: line 8: epatch_user: command not found
  9. >>> Messages generated by process 9066 on 2017-09-12 10:47:43 CEST for package media-libs/faad2-2.7-r3:
  11. QA: prepare
  12. This package has a configure.in file which has long been deprecated. Please
  13. update it to use configure.ac instead as newer versions of autotools will die
  14. when it finds this file. See https://bugs.gentoo.org/426262 for details.
  16. >>> Messages generated by process 9066 on 2017-09-12 10:48:10 CEST for package app-i18n/libguess-1.2:
  18. QA: install
  19. QA Notice: command not found:
  21. /etc/portage/bashrc: line 8: epatch_user: command not found
  23. >>> Messages generated by process 9066 on 2017-09-12 10:48:22 CEST for package media-libs/adplug-2.2.1:
  25. QA: install
  26. QA Notice: command not found:
  28. /etc/portage/bashrc: line 8: epatch_user: command not found
  29. QA: other
  30. QA Notice: Package triggers severe warnings which indicate that it
  31. may exhibit random runtime failures.
  32. fmopl.c:601:20: warning: iteration 15u invokes undefined behavior [-Waggressive-loop-optimizations]
  33. mid.cpp:873:53: warning: iteration 14u invokes undefined behavior [-Waggressive-loop-optimizations]
  34. Please do not file a Gentoo bug and instead report the above QA
  35. issues directly to the upstream developers of this software.
  36. Homepage: http://adplug.sourceforge.net
  38. >>> Messages generated by process 9066 on 2017-09-12 10:48:50 CEST for package media-sound/audacious-3.7.1:
  40. QA: install
  41. QA Notice: Unrecognized configure options:
  43. --enable-chardet
  44. --enable-chardet
  46. >>> Messages generated by process 9066 on 2017-09-12 10:49:18 CEST for package media-plugins/audacious-plugins-3.7.1:
  48. QA: install
  49. QA Notice: Unrecognized configure options:
  51. --enable-statusicon
  52. --enable-adplug
  53. --enable-statusicon
  54. --enable-adplug
  56. >>> Messages generated by process 1365 on 2017-09-12 11:06:01 CEST for package media-video/mpv-0.25.0-r2:
  58. LOG: postinst
  59. If you want to have command-line completion via bash-completion,
  60. please install app-shells/mpv-bash-completion.
  62. >>> Messages generated by process 18893 on 2017-09-12 11:19:45 CEST for package app-eselect/eselect-opencl-1.1.0-r1:
  64. QA: install
  65. QA Notice: command not found:
  67. /etc/portage/bashrc: line 8: epatch_user: command not found
  69. >>> Messages generated by process 18893 on 2017-09-12 11:21:33 CEST for package virtual/linux-sources-3:
  71. QA: install
  72. QA Notice: command not found:
  74. /etc/portage/bashrc: line 8: epatch_user: command not found
  76. >>> Messages generated by process 18893 on 2017-09-12 11:24:15 CEST for package sys-power/acpid-2.0.28:
  78. LOG: postinst
  80. You may wish to read the Gentoo Linux Power Management Guide,
  81. which can be found online at:
  82. https://wiki.gentoo.org/wiki/Power_management/Guide
  84. WARN: postinst
  85. You should reboot the system now to get /run mounted with tmpfs!
  87. >>> Messages generated by process 18884 on 2017-09-12 11:24:44 CEST for package sys-devel/llvm-3.9.1-r1:
  89. QA: other
  90. QA Notice: The following shared libraries lack NEEDED entries
  91. /usr/lib32/libLLVMGlobalISel.so.39.1
  92. /usr/lib64/libLLVMGlobalISel.so.39.1
  94. >>> Messages generated by process 18884 on 2017-09-12 11:25:03 CEST for package net-wireless/wpa_supplicant-2.6-r2:
  96. LOG: postinst
  97. If this is a clean installation of wpa_supplicant, you
  98. have to create a configuration file named
  99. /etc/wpa_supplicant/wpa_supplicant.conf
  101. An example configuration file is available for reference in
  102. /usr/share/doc/wpa_supplicant-2.6-r2/
  104. >>> Messages generated by process 18893 on 2017-09-12 11:25:32 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  106. ERROR: compile
  107. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase):
  108. emake failed
  110. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  111. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  112. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  113. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'.
  114. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel'
  115. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  117. >>> Messages generated by process 18884 on 2017-09-12 11:31:00 CEST for package net-analyzer/wireshark-2.2.7:
  119. WARN: postinst
  120. NOTE: To capture traffic with wireshark as normal user you have to
  121. add yourself to the wireshark group. This security measure ensures
  122. that only trusted users are allowed to sniff your traffic.
  124. >>> Messages generated by process 18884 on 2017-09-12 11:31:53 CEST for package app-editors/emacs-25.2:
  126. WARN: configure
  127. USE flag "alsa" overrides "-sound"; enabling sound support.
  128. Your version of GTK+ will have problems with closing open
  129. displays. This is no problem if you just use one display, but
  130. if you use more than one and close one of them Emacs may crash.
  131. See <https://bugzilla.gnome.org/show_bug.cgi?id=85715>.
  132. If you intend to use more than one display, then it is strongly
  133. recommended that you compile Emacs with the Athena/Lucid or the
  134. Motif toolkit instead.
  136. >>> Messages generated by process 18884 on 2017-09-12 11:32:20 CEST for package app-admin/conky-1.10.4:
  138. ERROR: configure
  139. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  140. cmake failed
  142. Call stack:
  143. ebuild.sh, line 115: Called src_configure
  144. environment, line 3800: Called cmake-utils_src_configure
  145. environment, line 1238: Called die
  146. The specific snippet of code:
  147. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  149. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  150. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  151. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  152. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  153. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  154. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  156. >>> Messages generated by process 18884 on 2017-09-12 11:32:55 CEST for package app-crypt/pinentry-0.9.7-r1:
  158. QA: other
  159. QA Notice: Package triggers severe warnings which indicate that it
  160. may exhibit random runtime failures.
  161. pinentry-curses.c:110:18: warning: implicit declaration of function 'addnwstr' [-Wimplicit-function-declaration]
  162. Please do not file a Gentoo bug and instead report the above QA
  163. issues directly to the upstream developers of this software.
  164. Homepage: http://gnupg.org/aegypten2/index.html
  166. >>> Messages generated by process 6620 on 2017-09-12 14:36:37 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  168. ERROR: setup
  169. These sources have not yet been prepared.
  170. We cannot build against an unprepared tree.
  171. To resolve this, please type the following:
  173. # cd /usr/src/linux
  174. # make oldconfig
  175. # make modules_prepare
  177. Then please try merging this module again.
  178. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase):
  179. Kernel sources need compiling first
  181. Call stack:
  182. ebuild.sh, line 115: Called pkg_setup
  183. nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup
  184. linux-mod.eclass, line 573: Called check_kernel_built
  185. linux-info.eclass, line 663: Called die
  186. The specific snippet of code:
  187. die "Kernel sources need compiling first"
  189. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  190. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  191. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  192. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'.
  193. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir'
  194. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  196. >>> Messages generated by process 10450 on 2017-09-12 14:37:16 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  198. ERROR: setup
  199. These sources have not yet been prepared.
  200. We cannot build against an unprepared tree.
  201. To resolve this, please type the following:
  203. # cd /usr/src/linux
  204. # make oldconfig
  205. # make modules_prepare
  207. Then please try merging this module again.
  208. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase):
  209. Kernel sources need compiling first
  211. Call stack:
  212. ebuild.sh, line 115: Called pkg_setup
  213. nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup
  214. linux-mod.eclass, line 573: Called check_kernel_built
  215. linux-info.eclass, line 663: Called die
  216. The specific snippet of code:
  217. die "Kernel sources need compiling first"
  219. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  220. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  221. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  222. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'.
  223. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir'
  224. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  226. >>> Messages generated by process 12941 on 2017-09-12 14:40:19 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  228. ERROR: setup
  229. These sources have not yet been prepared.
  230. We cannot build against an unprepared tree.
  231. To resolve this, please type the following:
  233. # cd /usr/src/linux
  234. # make oldconfig
  235. # make modules_prepare
  237. Then please try merging this module again.
  238. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase):
  239. Kernel sources need compiling first
  241. Call stack:
  242. ebuild.sh, line 115: Called pkg_setup
  243. nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup
  244. linux-mod.eclass, line 573: Called check_kernel_built
  245. linux-info.eclass, line 663: Called die
  246. The specific snippet of code:
  247. die "Kernel sources need compiling first"
  249. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  250. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  251. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  252. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'.
  253. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir'
  254. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  256. >>> Messages generated by process 15380 on 2017-09-12 14:42:50 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  258. ERROR: setup
  259. These sources have not yet been prepared.
  260. We cannot build against an unprepared tree.
  261. To resolve this, please type the following:
  263. # cd /usr/src/linux
  264. # make oldconfig
  265. # make modules_prepare
  267. Then please try merging this module again.
  268. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (setup phase):
  269. Kernel sources need compiling first
  271. Call stack:
  272. ebuild.sh, line 115: Called pkg_setup
  273. nvidia-drivers-384.59-r1.ebuild, line 142: Called linux-mod_pkg_setup
  274. linux-mod.eclass, line 573: Called check_kernel_built
  275. linux-info.eclass, line 663: Called die
  276. The specific snippet of code:
  277. die "Kernel sources need compiling first"
  279. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  280. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  281. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  282. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/die.env'.
  283. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/homedir'
  284. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  286. >>> Messages generated by process 17881 on 2017-09-12 14:44:10 CEST for package x11-drivers/nvidia-drivers-384.69:
  288. ERROR: setup
  289. These sources have not yet been prepared.
  290. We cannot build against an unprepared tree.
  291. To resolve this, please type the following:
  293. # cd /usr/src/linux
  294. # make oldconfig
  295. # make modules_prepare
  297. Then please try merging this module again.
  298. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (setup phase):
  299. Kernel sources need compiling first
  301. Call stack:
  302. ebuild.sh, line 115: Called pkg_setup
  303. nvidia-drivers-384.69.ebuild, line 142: Called linux-mod_pkg_setup
  304. linux-mod.eclass, line 573: Called check_kernel_built
  305. linux-info.eclass, line 663: Called die
  306. The specific snippet of code:
  307. die "Kernel sources need compiling first"
  309. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  310. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  311. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  312. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/die.env'.
  313. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/homedir'
  314. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  316. >>> Messages generated by process 13864 on 2017-09-12 15:07:03 CEST for package x11-drivers/nvidia-drivers-384.69:
  318. ERROR: compile
  319. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  320. emake failed
  322. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  323. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  324. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  325. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  326. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  327. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  329. >>> Messages generated by process 20321 on 2017-09-12 15:09:22 CEST for package x11-drivers/nvidia-drivers-384.69:
  331. ERROR: compile
  332. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  333. emake failed
  335. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  336. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  337. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  338. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  339. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  340. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  342. >>> Messages generated by process 26777 on 2017-09-12 15:12:27 CEST for package x11-drivers/nvidia-drivers-384.69:
  344. ERROR: compile
  345. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  346. emake failed
  348. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  349. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  350. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  351. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  352. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  353. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  355. >>> Messages generated by process 779 on 2017-09-12 15:14:06 CEST for package x11-drivers/nvidia-drivers-384.69:
  357. ERROR: compile
  358. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  359. emake failed
  361. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  362. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  363. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  364. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  365. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  366. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  368. >>> Messages generated by process 7396 on 2017-09-12 15:20:10 CEST for package x11-drivers/nvidia-drivers-384.69:
  370. ERROR: compile
  371. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  372. emake failed
  374. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  375. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  376. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  377. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  378. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  379. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  381. >>> Messages generated by process 13876 on 2017-09-12 15:23:32 CEST for package x11-base/xorg-drivers-1.19:
  383. QA: install
  384. QA Notice: command not found:
  386. /etc/portage/bashrc: line 8: epatch_user: command not found
  388. >>> Messages generated by process 13876 on 2017-09-12 15:24:25 CEST for package x11-drivers/nvidia-drivers-384.69:
  390. ERROR: compile
  391. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  392. emake failed
  394. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  395. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  396. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  397. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  398. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  399. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  401. >>> Messages generated by process 13876 on 2017-09-12 15:27:10 CEST for package media-libs/mesa-17.0.6:
  403. ERROR: compile
  404. ERROR: media-libs/mesa-17.0.6::gentoo failed (compile phase):
  405. emake failed
  407. If you need support, post the output of `emerge --info '=media-libs/mesa-17.0.6::gentoo'`,
  408. the complete build log and the output of `emerge -pqv '=media-libs/mesa-17.0.6::gentoo'`.
  409. The complete build log is located at '/var/tmp/portage/media-libs/mesa-17.0.6/temp/build.log'.
  410. The ebuild environment file is located at '/var/tmp/portage/media-libs/mesa-17.0.6/temp/environment'.
  411. Working directory: '/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6-abi_x86_32.x86'
  412. S: '/var/tmp/portage/media-libs/mesa-17.0.6/work/mesa-17.0.6'
  414. >>> Messages generated by process 924 on 2017-09-12 15:28:31 CEST for package x11-base/xorg-drivers-1.19:
  416. QA: install
  417. QA Notice: command not found:
  419. /etc/portage/bashrc: line 8: epatch_user: command not found
  421. >>> Messages generated by process 924 on 2017-09-12 15:34:14 CEST for package media-libs/mesa-17.0.6:
  423. LOG: postinst
  424. USE="bindist" was not set. Potentially patent encumbered code was
  425. enabled. Please see patents.txt for an explanation.
  426. Note that in order to have full S3TC support, it is necessary to install
  427. media-libs/libtxc_dxtn as well. This may be necessary to get nice
  428. textures in some apps, and some others even require this to run.
  430. >>> Messages generated by process 924 on 2017-09-12 17:30:14 CEST for package www-client/chromium-61.0.3163.79:
  432. ERROR: setup
  433. USER_NS is required for sandbox to work
  434. CONFIG_COMPAT_VDSO causes segfaults (bug #556286)
  435. WARN: setup
  436. Please check to make sure these options are set correctly.
  437. Failure to do so may cause unexpected problems.
  439. >>> Messages generated by process 924 on 2017-09-12 17:30:17 CEST for package app-admin/conky-1.10.4:
  441. ERROR: configure
  442. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  443. cmake failed
  445. Call stack:
  446. ebuild.sh, line 115: Called src_configure
  447. environment, line 3787: Called cmake-utils_src_configure
  448. environment, line 1225: Called die
  449. The specific snippet of code:
  450. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  452. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  453. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  454. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  455. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  456. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  457. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  459. >>> Messages generated by process 924 on 2017-09-12 17:31:03 CEST for package dev-qt/qtwebkit-5.7.1:
  461. ERROR: compile
  462. ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase):
  463. emake failed
  465. If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`,
  466. the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`.
  467. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'.
  468. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'.
  469. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  470. S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  472. >>> Messages generated by process 924 on 2017-09-12 17:32:31 CEST for package x11-misc/lightdm-1.18.3:
  474. QA: other
  476. This package seems to install gtk-doc documentation into the following
  477. location(s):
  479. /usr/share/doc/lightdm-1.18.3/html/lightdm-gobject-1
  481. gtk-doc documentation must always be installed into /usr/share/gtk-doc.
  482. For more details, please see the GNOME team policy page:
  483. https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies#gtk-doc
  486. >>> Messages generated by process 6955 on 2017-09-13 14:35:52 CEST for package www-client/firefox-52.3.0:
  488. LOG: setup
  489. You are enabling official branding. You may not redistribute this build
  490. to any users on your network or the internet. Doing so puts yourself into
  491. a legal problem with Mozilla Foundation
  492. You can disable it by emerging firefox _with_ the bindist USE-flag
  494. >>> Messages generated by process 30989 on 2017-09-13 16:00:05 CEST for package x11-base/xorg-drivers-1.19:
  496. QA: install
  497. QA Notice: command not found:
  499. /etc/portage/bashrc: line 8: epatch_user: command not found
  501. >>> Messages generated by process 30989 on 2017-09-13 16:01:01 CEST for package x11-drivers/nvidia-drivers-384.69:
  503. ERROR: compile
  504. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  505. emake failed
  507. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  508. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  509. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  510. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  511. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  512. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  514. >>> Messages generated by process 30989 on 2017-09-13 16:06:25 CEST for package media-libs/mesa-17.0.6:
  516. LOG: postinst
  517. USE="bindist" was not set. Potentially patent encumbered code was
  518. enabled. Please see patents.txt for an explanation.
  519. Note that in order to have full S3TC support, it is necessary to install
  520. media-libs/libtxc_dxtn as well. This may be necessary to get nice
  521. textures in some apps, and some others even require this to run.
  523. >>> Messages generated by process 30989 on 2017-09-13 16:06:28 CEST for package app-admin/conky-1.10.4:
  525. ERROR: configure
  526. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  527. cmake failed
  529. Call stack:
  530. ebuild.sh, line 115: Called src_configure
  531. environment, line 3800: Called cmake-utils_src_configure
  532. environment, line 1238: Called die
  533. The specific snippet of code:
  534. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  536. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  537. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  538. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  539. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  540. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  541. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  543. >>> Messages generated by process 30989 on 2017-09-13 16:06:47 CEST for package dev-qt/qtwebkit-5.7.1:
  545. ERROR: compile
  546. ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase):
  547. emake failed
  549. If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`,
  550. the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`.
  551. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'.
  552. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'.
  553. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  554. S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  556. >>> Messages generated by process 10962 on 2017-09-13 16:19:32 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  558. ERROR: compile
  559. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase):
  560. emake failed
  562. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  563. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  564. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  565. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'.
  566. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel'
  567. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  569. >>> Messages generated by process 10962 on 2017-09-13 16:22:58 CEST for package app-admin/conky-1.10.4:
  571. ERROR: configure
  572. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  573. cmake failed
  575. Call stack:
  576. ebuild.sh, line 115: Called src_configure
  577. environment, line 3800: Called cmake-utils_src_configure
  578. environment, line 1238: Called die
  579. The specific snippet of code:
  580. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  582. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  583. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  584. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  585. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  586. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  587. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  589. >>> Messages generated by process 10962 on 2017-09-13 16:23:17 CEST for package dev-qt/qtwebkit-5.7.1:
  591. ERROR: compile
  592. ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase):
  593. emake failed
  595. If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`,
  596. the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`.
  597. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'.
  598. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'.
  599. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  600. S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  602. >>> Messages generated by process 22721 on 2017-09-13 16:38:06 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  604. ERROR: compile
  605. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase):
  606. emake failed
  608. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  609. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  610. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  611. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'.
  612. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel'
  613. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  615. >>> Messages generated by process 30037 on 2017-09-13 16:54:21 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  617. ERROR: compile
  618. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase):
  619. emake failed
  621. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  622. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  623. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  624. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'.
  625. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel'
  626. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  628. >>> Messages generated by process 6076 on 2017-09-13 16:57:35 CEST for package x11-drivers/nvidia-drivers-384.59-r1:
  630. ERROR: compile
  631. ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (compile phase):
  632. emake failed
  634. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`,
  635. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.59-r1::gentoo'`.
  636. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'.
  637. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/environment'.
  638. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/kernel'
  639. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
  641. >>> Messages generated by process 6076 on 2017-09-13 16:57:46 CEST for package app-admin/conky-1.10.4:
  643. ERROR: configure
  644. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  645. cmake failed
  647. Call stack:
  648. ebuild.sh, line 115: Called src_configure
  649. environment, line 3800: Called cmake-utils_src_configure
  650. environment, line 1238: Called die
  651. The specific snippet of code:
  652. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  654. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  655. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  656. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  657. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  658. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  659. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  661. >>> Messages generated by process 6076 on 2017-09-13 16:58:06 CEST for package dev-qt/qtwebkit-5.7.1:
  663. ERROR: compile
  664. ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase):
  665. emake failed
  667. If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`,
  668. the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`.
  669. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'.
  670. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'.
  671. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  672. S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  674. >>> Messages generated by process 7688 on 2017-09-14 14:16:05 CEST for package x11-drivers/nvidia-drivers-384.69:
  676. ERROR: compile
  677. ERROR: x11-drivers/nvidia-drivers-384.69::gentoo failed (compile phase):
  678. emake failed
  680. If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-384.69::gentoo'`,
  681. the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-384.69::gentoo'`.
  682. The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/build.log'.
  683. The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/temp/environment'.
  684. Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/kernel'
  685. S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.69/work/'
  687. >>> Messages generated by process 7688 on 2017-09-14 14:16:17 CEST for package app-admin/conky-1.10.4:
  689. ERROR: configure
  690. ERROR: app-admin/conky-1.10.4::gentoo failed (configure phase):
  691. cmake failed
  693. Call stack:
  694. ebuild.sh, line 115: Called src_configure
  695. environment, line 3800: Called cmake-utils_src_configure
  696. environment, line 1238: Called die
  697. The specific snippet of code:
  698. "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
  700. If you need support, post the output of `emerge --info '=app-admin/conky-1.10.4::gentoo'`,
  701. the complete build log and the output of `emerge -pqv '=app-admin/conky-1.10.4::gentoo'`.
  702. The complete build log is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/build.log'.
  703. The ebuild environment file is located at '/var/tmp/portage/app-admin/conky-1.10.4/temp/environment'.
  704. Working directory: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4_build'
  705. S: '/var/tmp/portage/app-admin/conky-1.10.4/work/conky-1.10.4'
  707. >>> Messages generated by process 7688 on 2017-09-14 14:16:38 CEST for package dev-qt/qtwebkit-5.7.1:
  709. ERROR: compile
  710. ERROR: dev-qt/qtwebkit-5.7.1::gentoo failed (compile phase):
  711. emake failed
  713. If you need support, post the output of `emerge --info '=dev-qt/qtwebkit-5.7.1::gentoo'`,
  714. the complete build log and the output of `emerge -pqv '=dev-qt/qtwebkit-5.7.1::gentoo'`.
  715. The complete build log is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/build.log'.
  716. The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/temp/environment'.
  717. Working directory: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  718. S: '/var/tmp/portage/dev-qt/qtwebkit-5.7.1/work/qtwebkit-opensource-src-5.7.1'
  719.  
Powered by spacepaste. Paste removal.