View previous topic :: View next topic |
Author |
Message |
papas Tux's lil' helper
Joined: 01 Dec 2014 Posts: 141 Location: Athens
|
Posted: Wed Aug 16, 2017 7:42 am Post subject: [SOLVED] nvidia-drivers failed to build |
|
|
Hello,
nvidia-driver-384-59-r1 failed to build (during the last update).
the error is:
Code: |
hardened andreas # emerge -avqDu nvidia-drivers
[ebuild U ] x11-drivers/nvidia-drivers-384.59-r1 [381.22] USE="X acpi driver kms multilib pax_kernel tools -compat -gtk3 -static-libs -uvm -wayland" ABI_X86="32 (64) (-x32)"
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-drivers/nvidia-drivers-384.59-r1
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/4.9.24-hardened/build
* Found sources for kernel version:
* 4.9.24-hardened
* Checking for suitable kernel configuration options... [ ok ]
>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-384.59-r1::gentoo
>>> Failed to emerge x11-drivers/nvidia-drivers-384.59-r1, Log file:
>>> '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/temp/build.log'
>>> Jobs: 0 of 1 complete, 1 failed Load avg: 2.49, 2.69, 2.59
* Package: x11-drivers/nvidia-drivers-384.59-r1
* Repository: gentoo
* Maintainer: jer@gentoo.org hardened@gentoo.org
* USE: X abi_x86_32 abi_x86_64 acpi amd64 driver elibc_glibc kernel_linux kms multilib pax_kernel tools userland_GNU
* FEATURES: preserve-libs sandbox selinux sesandbox userpriv usersandbox
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/4.9.24-hardened/build
* Found sources for kernel version:
* 4.9.24-hardened
* Checking for suitable kernel configuration options...
[ ok ]
* Checking for suitable kernel configuration options...
[ ok ]
>>> Unpacking NVIDIA-Linux-x86_64-384.59.run to /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work
>>> Unpacking nvidia-settings-384.59.tar.gz to /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work
* Using PAX patches is not supported. You will be asked to
* use a standard kernel should you have issues. Should you
* need support with these patches, contact the PaX team.
* Applying nvidia-drivers-375.20-pax.patch ...
The text leading up to this was:
--------------------------
|diff -urp work.orig/kernel/nvidia-uvm/uvm_full_fault_buffer.h work/kernel/nvidia-uvm/uvm_full_fault_buffer.h
|--- work.orig/kernel/nvidia-uvm/uvm_full_fault_buffer.h 2016-11-27 21:56:50.399642330 +0100
|+++ work/kernel/nvidia-uvm/uvm_full_fault_buffer.h 2016-11-27 21:54:23.975709978 +0100
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
[ !! ]
* ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (prepare phase):
* patch -p1 failed with /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch
*
* Call stack:
* ebuild.sh, line 115: Called src_prepare
* environment, line 5003: Called eapply '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* environment, line 1277: Called _eapply_patch '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* environment, line 1215: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* 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'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
* Messages for package x11-drivers/nvidia-drivers-384.59-r1:
* Using PAX patches is not supported. You will be asked to
* use a standard kernel should you have issues. Should you
* need support with these patches, contact the PaX team.
* ERROR: x11-drivers/nvidia-drivers-384.59-r1::gentoo failed (prepare phase):
* patch -p1 failed with /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch
*
* Call stack:
* ebuild.sh, line 115: Called src_prepare
* environment, line 5003: Called eapply '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* environment, line 1277: Called _eapply_patch '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* environment, line 1215: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/files/nvidia-drivers-375.20-pax.patch'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* 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'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-384.59-r1/work/'
|
I'm using hardened-4.9.24-sources (~amd64) but I'm getting same error with hardened-4.8-17-r2 which is stable, any idea ?
Last edited by papas on Wed Aug 16, 2017 8:04 am; edited 1 time in total |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30838 Location: here
|
Posted: Wed Aug 16, 2017 7:51 am Post subject: |
|
|
Code: | * Using PAX patches is not supported. You will be asked to
* use a standard kernel should you have issues. Should you
* need support with these patches, contact the PaX team.
* Applying nvidia-drivers-375.20-pax.patch ... |
Or you should create an ebuild on your local overlay, download patch proposed here rename it in nvidia-drivers-384.xx-pax.patch, and finally change chunk of ebuild code in src_prepare function from
Code: | src_prepare() {
if use pax_kernel; then
ewarn "Using PAX patches is not supported. You will be asked to"
ewarn "use a standard kernel should you have issues. Should you"
ewarn "need support with these patches, contact the PaX team."
eapply "${FILESDIR}"/${PN}-375.20-pax.patch
fi
... |
to
Code: | src_prepare() {
if use pax_kernel; then
ewarn "Using PAX patches is not supported. You will be asked to"
ewarn "use a standard kernel should you have issues. Should you"
ewarn "need support with these patches, contact the PaX team."
eapply "${FILESDIR}"/${PN}-384.xx-pax.patch
fi
... |
_________________ Questions are guaranteed in life; Answers aren't.
Last edited by fedeliallalinea on Wed Aug 16, 2017 7:53 am; edited 1 time in total |
|
Back to top |
|
|
papas Tux's lil' helper
Joined: 01 Dec 2014 Posts: 141 Location: Athens
|
Posted: Wed Aug 16, 2017 7:52 am Post subject: |
|
|
thank you |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|