diabolusUmarov

Untitled

Jun 11th, 2017
314
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.50 KB | None | 0 0
  1.  * Package: x11-drivers/nvidia-drivers-340.102
  2.  * Repository: gentoo
  3.  * Maintainer: [email protected] [email protected]
  4.  * USE: X abi_x86_32 abi_x86_64 acpi amd64 elibc_glibc kernel_linux multilib static-libs tools userland_GNU uvm
  5.  * FEATURES: preserve-libs sandbox userpriv usersandbox
  6. * Determining the location of the kernel source code
  7. * Found kernel source directory:
  8. * /usr/src/linux
  9. * Found kernel object directory:
  10. * /lib/modules/4.9.30-gentoo/build
  11. * Found sources for kernel version:
  12. * 4.9.30-gentoo
  13. * Checking for suitable kernel configuration options...
  14.  [ ok ]
  15. * Checking for suitable kernel configuration options...
  16.  [ ok ]
  17. >>> Unpacking source...
  18. >>> Unpacking NVIDIA-Linux-x86_64-340.102.run to /var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work
  19. >>> Unpacking nvidia-settings-340.102.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work
  20. >>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work
  21. >>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work ...
  22. * Applying patches from /etc/portage/patches/x11-drivers/nvidia-drivers-340.102 ...
  23. * nvidia-340-kernel-4.9-fix.patch ...
  24. The text leading up to this was:
  25. --------------------------
  26. |--- kernel/nv-drm.c 2016-12-15 12:41:26.000000000 +0100
  27. |+++ kernel/nv-drm.c 2016-12-15 12:58:48.000000000 +0100
  28. --------------------------
  29. No file to patch. Skipping patch.
  30. patch unexpectedly ends in middle of line
  31. 1 out of 1 hunk ignored
  32.  [ !! ]
  33. * ERROR: x11-drivers/nvidia-drivers-340.102::gentoo failed (prepare phase):
  34. * patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-340.102/nvidia-340-kernel-4.9-fix.patch
  35. *
  36. * Call stack:
  37. * ebuild.sh, line 115: Called src_prepare
  38. * environment, line 4975: Called eapply_user
  39. * environment, line 1265: Called eapply '/etc/portage/patches/x11-drivers/nvidia-drivers-340.102'
  40. * environment, line 1242: Called _eapply_patch '/etc/portage/patches/x11-drivers/nvidia-drivers-340.102/nvidia-340-kernel-4.9-fix.patch' ' '
  41. * environment, line 1184: Called __helpers_die 'patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-340.102/nvidia-340-kernel-4.9-fix.patch'
  42. * isolated-functions.sh, line 117: Called die
  43. * The specific snippet of code:
  44. * die "$@"
  45. *
  46. * If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-340.102::gentoo'`,
  47. * the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-340.102::gentoo'`.
  48. * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-340.102/temp/build.log'.
  49. * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-340.102/temp/environment'.
  50. * Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work'
  51. * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-340.102/work/'
Advertisement
Add Comment
Please, Sign In to add comment