Advertisement
Guest User

Untitled

a guest
Jun 19th, 2019
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.45 KB | None | 0 0
  1. emerge -v1 =www-client/chromium-75.0.3770.80::pg_overlay
  2.  
  3. These are the packages that would be merged, in order:
  4.  
  5. Calculating dependencies... done!
  6. [ebuild U ] www-client/chromium-75.0.3770.80::pg_overlay [74.0.3729.169::localrepo] USE="cups custom-cflags hangouts jumbo-build (pic) proprietary-codecs pulseaudio suid system-ffmpeg system-icu system-libvpx tcmalloc vaapi widevine -closure-compile* -component-build -gnome-keyring -kerberos (-neon) (-selinux)" L10N="-am -ar -bg -bn -ca -cs -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" 691,392 KiB
  7.  
  8. Total: 1 package (1 upgrade), Size of downloads: 691,392 KiB
  9.  
  10. >>> Verifying ebuild manifests
  11. >>> Running pre-merge checks for www-client/chromium-75.0.3770.80
  12. * Checking for at least 3 GiB RAM ... [ ok ]
  13. * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/chromium-75.0.3770.80/temp" ... [ ok ]
  14. >>> Emerging (1 of 1) www-client/chromium-75.0.3770.80::pg_overlay
  15. >>> Failed to emerge www-client/chromium-75.0.3770.80, Log file:
  16. >>> '/var/log/portage.d/www-client:chromium-75.0.3770.80:20190608-122304.log'
  17. >>> Jobs: 0 of 1 complete, 1 failed Load avg: 3.57, 2.38, 1.47
  18. * Package: www-client/chromium-75.0.3770.80
  19. * Repository: pg_overlay
  20. * Maintainer: chromium@gentoo.org
  21. * USE: abi_x86_64 amd64 cups custom-cflags elibc_glibc hangouts jumbo-build kernel_linux pic proprietary-codecs pulseaudio suid system-ffmpeg system-icu system-libvpx tcmalloc userland_GNU vaapi widevine
  22. * FEATURES: ccache network-sandbox preserve-libs sandbox userpriv usersandbox
  23. www-client/chromium: 7 hours, 11 minutes, 12 seconds average for 6 merges
  24. www-client/chromium: 8 seconds average for 4 unmerges
  25. 2019-04-11T02:44:31 >>> www-client/chromium: 5 hours, 17 minutes, 55 seconds
  26. 2019-04-11T15:38:26 <<< www-client/chromium: 7 seconds
  27. 2019-04-11T18:12:25 >>> www-client/chromium: 6 hours, 1 minute, 23 seconds
  28. 2019-04-14T03:46:35 <<< www-client/chromium: 7 seconds
  29. 2019-04-17T02:07:57 >>> www-client/chromium: 11 hours, 45 minutes, 43 seconds
  30. 2019-04-21T22:45:02 <<< www-client/chromium: 16 seconds
  31. 2019-04-22T08:59:03 >>> www-client/chromium: 6 hours, 38 minutes, 1 second
  32. 2019-05-15T18:26:20 >>> www-client/chromium: 8 hours, 15 minutes, 51 seconds
  33. 2019-05-22T17:46:38 <<< www-client/chromium: 3 seconds
  34. 2019-05-22T21:54:52 >>> www-client/chromium: 5 hours, 8 minutes, 21 seconds
  35. * FEATURES='assume-digests binpkg-docompress binpkg-dostrip binpkg-logs ccache config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr'
  36. * CFLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  37. * CXXFLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  38. * CPPFLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  39. * FFLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  40. * FCFLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  41. * F77FLAGS='-march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -flto=thin -fstack-check'
  42. * LDFLAGS='-Wl,-O2 -Wl,--as-needed -Wl,--strip-debug -flto=thin -Wl,--thinlto-jobs=3 -fuse-ld=lld -march=native -mtune=native -O3 -pipe -fomit-frame-pointer -fno-stack-protector -fstack-check'
  43. * MAKEOPTS='-j3'
  44. * USE_NONGNU='1'
  45. * gcc (Gentoo 9.1.0-r1 p1.1) 9.1.0
  46. * Linux igloo-l440 5.1.7-jsX #1 SMP PREEMPT Fri Jun 7 22:30:18 AST 2019 x86_64 Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz GenuineIntel GNU/Linux
  47. * Checking for at least 3 GiB RAM ...
  48. [ ok ]
  49. * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/chromium-75.0.3770.80/temp" ...
  50. [ ok ]
  51. * Determining the location of the kernel source code
  52. * Found kernel source directory:
  53. * /usr/src/linux
  54. * Found sources for kernel version:
  55. * 5.1.7-jsX
  56. * Checking for suitable kernel configuration options...
  57. [ ok ]
  58. >>> Unpacking source...
  59. >>> Unpacking chromium-75.0.3770.80.tar.xz to /var/tmp/portage/www-client/chromium-75.0.3770.80/work
  60. >>> Source unpacked in /var/tmp/portage/www-client/chromium-75.0.3770.80/work
  61. >>> Preparing source in /var/tmp/portage/www-client/chromium-75.0.3770.80/work/chromium-75.0.3770.80 ...
  62. * Applying chromium-libusb_interrupt_event_handler.patch ...
  63. [ ok ]
  64. * Applying chromium-dma-buf.patch ...
  65. [ ok ]
  66. * Applying chromium-non-void-return.patch ...
  67. [ ok ]
  68. * Applying chromium-drm.patch ...
  69. [ ok ]
  70. * Applying chromium-sandbox-pie.patch ...
  71. [ ok ]
  72. * Applying chromium-system-icu.patch ...
  73. [ ok ]
  74. * Applying chromium-system-libusb.patch ...
  75. [ ok ]
  76. * Applying chromium-vaapi.patch ...
  77. [ ok ]
  78. * Applying chromium-skia-system-fontconfig.patch ...
  79. [ ok ]
  80. * Applying libstdc-do-not-assume-unique_ptr-has-ostream-operator.patch ...
  81. [ ok ]
  82. * Applying chromium-fix-window-flash-for-some-WMs.patch ...
  83. [ ok ]
  84. * Applying chromium-fix-the-flash-for-new-windows.patch ...
  85. [ ok ]
  86. * Applying chromium-fix-window-flash-for-some-WMs.patch ...
  87. 1 out of 1 hunk FAILED -- saving rejects to file ui/gl/BUILD.gn.rej
  88. 3 out of 3 hunks FAILED -- saving rejects to file ui/gl/gl_surface_glx.cc.rej
  89. [ !! ]
  90. * ERROR: www-client/chromium-75.0.3770.80::pg_overlay failed (prepare phase):
  91. * patch -p1 failed with /etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch
  92. *
  93. * Call stack:
  94. * ebuild.sh, line 124: Called src_prepare
  95. * environment, line 5614: Called default
  96. * phase-functions.sh, line 872: Called default_src_prepare
  97. * phase-functions.sh, line 937: Called __eapi6_src_prepare
  98. * environment, line 1682: Called eapply_user
  99. * environment, line 2858: Called eapply '/etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  100. * environment, line 2828: Called _eapply_patch '/etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  101. * environment, line 2766: Called __helpers_die 'patch -p1 failed with /etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  102. * isolated-functions.sh, line 119: Called die
  103. * The specific snippet of code:
  104. * die "$@"
  105. *
  106. * If you need support, post the output of `emerge --info '=www-client/chromium-75.0.3770.80::pg_overlay'`,
  107. * the complete build log and the output of `emerge -pqv '=www-client/chromium-75.0.3770.80::pg_overlay'`.
  108. * The complete build log is located at '/var/log/portage.d/www-client:chromium-75.0.3770.80:20190608-122304.log'.
  109. * For convenience, a symlink to the build log is located at '/var/tmp/portage/www-client/chromium-75.0.3770.80/temp/build.log'.
  110. * The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-75.0.3770.80/temp/environment'.
  111. * Working directory: '/var/tmp/portage/www-client/chromium-75.0.3770.80/work/chromium-75.0.3770.80'
  112. * S: '/var/tmp/portage/www-client/chromium-75.0.3770.80/work/chromium-75.0.3770.80'
  113.  
  114. * Messages for package www-client/chromium-75.0.3770.80:
  115. * Log file: /var/log/portage.d/www-client:chromium-75.0.3770.80:20190608-122304.log
  116.  
  117. * ERROR: www-client/chromium-75.0.3770.80::pg_overlay failed (prepare phase):
  118. * patch -p1 failed with /etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch
  119. *
  120. * Call stack:
  121. * ebuild.sh, line 124: Called src_prepare
  122. * environment, line 5614: Called default
  123. * phase-functions.sh, line 872: Called default_src_prepare
  124. * phase-functions.sh, line 937: Called __eapi6_src_prepare
  125. * environment, line 1682: Called eapply_user
  126. * environment, line 2858: Called eapply '/etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  127. * environment, line 2828: Called _eapply_patch '/etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  128. * environment, line 2766: Called __helpers_die 'patch -p1 failed with /etc/portage/patches/www-client/chromium/chromium-fix-window-flash-for-some-WMs.patch'
  129. * isolated-functions.sh, line 119: Called die
  130. * The specific snippet of code:
  131. * die "$@"
  132. *
  133. * If you need support, post the output of `emerge --info '=www-client/chromium-75.0.3770.80::pg_overlay'`,
  134. * the complete build log and the output of `emerge -pqv '=www-client/chromium-75.0.3770.80::pg_overlay'`.
  135. * The complete build log is located at '/var/log/portage.d/www-client:chromium-75.0.3770.80:20190608-122304.log'.
  136. * For convenience, a symlink to the build log is located at '/var/tmp/portage/www-client/chromium-75.0.3770.80/temp/build.log'.
  137. * The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-75.0.3770.80/temp/environment'.
  138. * Working directory: '/var/tmp/portage/www-client/chromium-75.0.3770.80/work/chromium-75.0.3770.80'
  139. * S: '/var/tmp/portage/www-client/chromium-75.0.3770.80/work/chromium-75.0.3770.80'
  140. igloo-l440 ~ # www-client/chromium-75.0.3770.80::pg_overlay
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement