From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
Date: Mon, 19 Mar 2012 12:12:29 -0400 [thread overview]
Message-ID: <20120319121229.0a9ecd3b.frank.peters@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
the plain vanilla source.
After rebooting to the command console, and before starting X, I needed
to re-install the nvidia-driver module for the new kernel. Doing
"emerge nvidia-drivers" gave me the following error (the entire build log
is attached):
>>> Source prepared.
>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>> Source configured.
>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
Preparing nvidia module
make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
*** Unable to determine the target kernel version. ***
make: *** [select_makefile] Error 1
emake failed
ERROR: x11-drivers/nvidia-drivers-295.20-r1 failed (compile phase):
Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
Call stack:
ebuild.sh, line 85: Called src_compile
environment, line 3711: Called linux-mod_src_compile
environment, line 2668: Called die
The specific snippet of code:
eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
The first part of the build log (see attached file) indicates that the
kernel source was correctly found (at /usr/src/linux), but for some
reason the make process fails.
Could this be due to some changes in the kernel-3.3.0 tree?
Frank Peters
[-- Attachment #2: nvidia-build.log --]
[-- Type: text/plain, Size: 4231 bytes --]
^[[32;01m * ^[[39;49;00mPackage: x11-drivers/nvidia-drivers-295.20-r1
^[[32;01m * ^[[39;49;00mRepository: gentoo
^[[32;01m * ^[[39;49;00mMaintainer: cardoe@gentoo.org jer@gentoo.org,spock@gentoo.org,xarthisius@gentoo.org
^[[32;01m * ^[[39;49;00mUSE: amd64 elibc_glibc kernel_linux userland_GNU
^[[32;01m * ^[[39;49;00mFEATURES: sandbox
^[[32;01m*^[[0m Determining the location of the kernel source code
^[[32;01m*^[[0m Found kernel source directory:
^[[32;01m*^[[0m /usr/src/linux
^[[32;01m*^[[0m Found kernel object directory:
^[[32;01m*^[[0m /lib/modules/3.3.0/build
^[[32;01m*^[[0m Found sources for kernel version:
^[[32;01m*^[[0m 3.3.0
^[[32;01m*^[[0m Checking for MTRR support ...
^[[A^[[82C ^[[36m[ ^[[32;01mok^[[36m ]^[[0m
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-295.20.run to /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work
>>> Source unpacked in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work
>>> Preparing source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
^[[32;01m*^[[0m Applying 256.35-unified-arch.patch ...
^[[A^[[82C ^[[36m[ ^[[32;01mok^[[36m ]^[[0m
^[[32;01m*^[[0m Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...
^[[A^[[82C ^[[36m[ ^[[32;01mok^[[36m ]^[[0m
>>> Source prepared.
>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>> Source configured.
>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
^[[32;01m*^[[0m Preparing nvidia module
make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.
If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.
Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.
*** Unable to determine the target kernel version. ***
make: *** [select_makefile] Error 1
emake failed
^[[31;01m*^[[0m ERROR: x11-drivers/nvidia-drivers-295.20-r1 failed (compile phase):
^[[31;01m*^[[0m Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
^[[31;01m*^[[0m
^[[31;01m*^[[0m Call stack:
^[[31;01m*^[[0m ebuild.sh, line 85: Called src_compile
^[[31;01m*^[[0m environment, line 3711: Called linux-mod_src_compile
^[[31;01m*^[[0m environment, line 2668: Called die
^[[31;01m*^[[0m The specific snippet of code:
^[[31;01m*^[[0m eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
^[[31;01m*^[[0m
^[[31;01m*^[[0m If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-295.20-r1',
^[[31;01m*^[[0m the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-295.20-r1'.
^[[31;01m*^[[0m The complete build log is located at '/tmp/portage-acc/log/x11-drivers:nvidia-drivers-295.20-r1:20120319-144118.log'.
^[[31;01m*^[[0m The ebuild environment file is located at '/tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/temp/environment'.
^[[31;01m*^[[0m S: '/tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work/'
next reply other threads:[~2012-03-19 18:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:12 Frank Peters [this message]
2012-03-19 16:35 ` [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Mark Knecht
2012-03-19 19:05 ` Frank Peters
2012-03-19 19:16 ` Mark Knecht
2012-03-19 19:30 ` Frank Peters
2012-03-19 20:08 ` Mark Knecht
2012-03-19 20:25 ` Paul Hartman
2012-03-19 19:14 ` Cheng Renquan
2012-03-19 19:17 ` Mark Knecht
2012-03-19 21:28 ` Barry Schwartz
2012-03-19 21:40 ` Mark Knecht
2012-03-20 0:34 ` Barry Schwartz
2012-03-20 4:03 ` Frank Peters
2012-03-20 6:20 ` Barry Schwartz
2012-03-20 18:31 ` [gentoo-amd64] " Duncan
2012-03-20 18:27 ` Duncan
2012-03-22 16:03 ` [gentoo-amd64] " Mark Knecht
2012-03-22 18:41 ` Frank Peters
2012-03-22 18:58 ` Mark Knecht
2012-03-22 21:18 ` Barry Schwartz
2012-03-22 21:21 ` Barry Schwartz
2012-03-22 21:32 ` Outside of portage (was Re: [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers) Barry Schwartz
2012-03-22 23:04 ` Paul Hartman
2012-03-22 23:28 ` Barry Schwartz
2012-03-22 23:33 ` Harry Holt
2012-03-23 8:42 ` Benny Pedersen
2012-03-23 13:50 ` Harry Holt
2012-03-23 0:14 ` Gary E. Miller
2012-03-23 1:30 ` Mark Knecht
2012-03-23 1:56 ` Barry Schwartz
2012-03-23 4:05 ` [gentoo-amd64] Re: Outside of portage (was " Duncan
2012-03-23 12:41 ` Outside of portage (was Re: [gentoo-amd64] " Frank Peters
2012-03-23 15:49 ` Barry Schwartz
2012-03-23 18:09 ` Dale
2012-03-23 18:28 ` [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers Mark Knecht
2012-03-23 19:11 ` Mark Knecht
2012-03-24 0:20 ` Frank Peters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120319121229.0a9ecd3b.frank.peters@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox