[gentoo-user] nvidia-drivers-180.51 on amd64

[gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

Hello list,

My box is trying to upgrade nvidia-drivers to version 180.51, but I get 
this:

>>> Compiling source 
in /tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2 ...
 * Preparing nvidia module
make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc 
CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 
SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.29-gentoo-r1/build 
HOST_CC=x86_64-pc-linux-gnu-gcc clean module
[...]
*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
 *
 * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3792:  Called linux-mod_src_compile
 *             environment, line 2799:  Called die
 * The specific snippet of code:
 *               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}";

Can anyone see what the problem is? I did the upgrade of X to 1.5 a few 
weeks ago, and the /usr/src/linux link is correctly pointing to the current 
kernel.

This first happened yesterday, but I waited to see if it was still the same 
after the next daily sync. It is. I can't see a bugzilla entry for it; 
perhaps I should raise one.

-- 
Rgds
Peter

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Tue, 21 Apr 2009 10:48:11 +0100, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> Hello list,
> 
> My box is trying to upgrade nvidia-drivers to version 180.51, but I get 
> this:
> 
>>>> Compiling source 
> in
>
/tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2
> ...
>  * Preparing nvidia module
> make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc 
> CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 
> SYSSRC=skins/default/usr/src/linux
SYSOUT=/lib/modules/2.6.29-gentoo-r1/build 
> HOST_CC=x86_64-pc-linux-gnu-gcc clean module
> [...]
> *** Unable to determine the target kernel version. ***
> 
> make: *** [select_makefile] Error 1
>  *
>  * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
>  * Call stack:
>  *               ebuild.sh, line   49:  Called src_compile
>  *             environment, line 3792:  Called linux-mod_src_compile
>  *             environment, line 2799:  Called die
>  * The specific snippet of code:
>  *               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}";
> 
> Can anyone see what the problem is? I did the upgrade of X to 1.5 a few 
> weeks ago, and the /usr/src/linux link is correctly pointing to the
current

I think the problem is from the SYSSRC make paremeter which is set to
skins/default/usr/src/linux, which seems to be invalid.
Maybe you can check to your environment for the variable KBUILD_OUTPUT if i
remember correctly.

HTH

> kernel.
> 
> This first happened yesterday, but I waited to see if it was still the
same
> 
> after the next daily sync. It is. I can't see a bugzilla entry for it; 
> perhaps I should raise one.

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Justin]

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

Peter Humphrey schrieb:
> Hello list,
> 
> My box is trying to upgrade nvidia-drivers to version 180.51, but I get 
> this:
> 
>>>> Compiling source 
> in /tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2 ...
>  * Preparing nvidia module
> make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc 
> CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 
> SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.29-gentoo-r1/build 
> HOST_CC=x86_64-pc-linux-gnu-gcc clean module
> [...]
> *** Unable to determine the target kernel version. ***
> 
> make: *** [select_makefile] Error 1
>  *
>  * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
>  * Call stack:
>  *               ebuild.sh, line   49:  Called src_compile
>  *             environment, line 3792:  Called linux-mod_src_compile
>  *             environment, line 2799:  Called die
>  * The specific snippet of code:
>  *               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}";
> 
> Can anyone see what the problem is? I did the upgrade of X to 1.5 a few 
> weeks ago, and the /usr/src/linux link is correctly pointing to the current 
> kernel.
> 
> This first happened yesterday, but I waited to see if it was still the same 
> after the next daily sync. It is. I can't see a bugzilla entry for it; 
> perhaps I should raise one.
> 
Which kernel du you use?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Tue, 21 Apr 2009 11:57:04 +0200, Justin <justin@j-schmitz.net> wrote:
> Peter Humphrey schrieb:
>> Hello list,
>> 
>> My box is trying to upgrade nvidia-drivers to version 180.51, but I get 
>> this:
>> 
>>>>> Compiling source 
>> in
>>
/tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2
>> ...
>>  * Preparing nvidia module
>> make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc 
>> CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 
>> SYSSRC=skins/default/usr/src/linux
SYSOUT=/lib/modules/2.6.29-gentoo-r1/build 
>> HOST_CC=x86_64-pc-linux-gnu-gcc clean module
>> [...]
>> *** Unable to determine the target kernel version. ***
>> 
>> make: *** [select_makefile] Error 1
>>  *
>>  * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
>>  * Call stack:
>>  *               ebuild.sh, line   49:  Called src_compile
>>  *             environment, line 3792:  Called linux-mod_src_compile
>>  *             environment, line 2799:  Called die
>>  * The specific snippet of code:
>>  *               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}";
>> 
>> Can anyone see what the problem is? I did the upgrade of X to 1.5 a few 
>> weeks ago, and the /usr/src/linux link is correctly pointing to the
>> current
>> kernel.
>> 
>> This first happened yesterday, but I waited to see if it was still the
>> same
>> after the next daily sync. It is. I can't see a bugzilla entry for it; 
>> perhaps I should raise one.
>> 
> Which kernel du you use?

It seems to be 2.6.29-r1 according to SYSOUT content in the portage
output...

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Justin]

[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]

Xavier Parizet schrieb:
> On Tue, 21 Apr 2009 11:57:04 +0200, Justin <justin@j-schmitz.net> wrote:
>> Peter Humphrey schrieb:
>>> Hello list,
>>>
>>> My box is trying to upgrade nvidia-drivers to version 180.51, but I get 
>>> this:
>>>
>>>>>> Compiling source 
>>> in
>>>
> /tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2
>>> ...
>>>  * Preparing nvidia module
>>> make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc 
>>> CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 
>>> SYSSRC=skins/default/usr/src/linux
> SYSOUT=/lib/modules/2.6.29-gentoo-r1/build 
>>> HOST_CC=x86_64-pc-linux-gnu-gcc clean module
>>> [...]
>>> *** Unable to determine the target kernel version. ***
>>>
>>> make: *** [select_makefile] Error 1
>>>  *
>>>  * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
>>>  * Call stack:
>>>  *               ebuild.sh, line   49:  Called src_compile
>>>  *             environment, line 3792:  Called linux-mod_src_compile
>>>  *             environment, line 2799:  Called die
>>>  * The specific snippet of code:
>>>  *               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}";
>>>
>>> Can anyone see what the problem is? I did the upgrade of X to 1.5 a few 
>>> weeks ago, and the /usr/src/linux link is correctly pointing to the
>>> current
>>> kernel.
>>>
>>> This first happened yesterday, but I waited to see if it was still the
>>> same
>>> after the next daily sync. It is. I can't see a bugzilla entry for it; 
>>> perhaps I should raise one.
>>>
>> Which kernel du you use?
> 
> It seems to be 2.6.29-r1 according to SYSOUT content in the portage
> output...
> 
Yeah that why I am asking, I had an issue with a kernel module package which found the kernel source
from the new kernel but has a SYSOUT from the old and wanted to build against that. But sources were
already unmerged.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Tuesday 21 April 2009 10:56:25 Xavier Parizet wrote:

> I think the problem is from the SYSSRC make paremeter which is set to
> skins/default/usr/src/linux, which seems to be invalid.

Where did you get the "skins" part of that? It isn't in what I posted.

> Maybe you can check to your environment for the variable KBUILD_OUTPUT if
> i remember correctly.

I seem not to have one.

Maybe the problem is in "CROSS_COMPILE=x86_64-pc-linux-gnu-", which seems 
incomplete.

-- 
Rgds
Peter

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Tuesday 21 April 2009 12:21:52 Justin wrote:
> Xavier Parizet schrieb:
> > On Tue, 21 Apr 2009 11:57:04 +0200, Justin <justin@j-schmitz.net> wrote:
> >>
> >> Which kernel du you use?
> >
> > It seems to be 2.6.29-r1 according to SYSOUT content in the portage
> > output...
>
> Yeah that why I am asking, I had an issue with a kernel module package
> which found the kernel source from the new kernel but has a SYSOUT from
> the old and wanted to build against that. But sources were already
> unmerged.

2.6.29-r1 is correct.

(I hope I got the quoting right. Apologies if not.)

-- 
Rgds
Peter

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Tue, 21 Apr 2009 16:07:02 +0100, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> On Tuesday 21 April 2009 10:56:25 Xavier Parizet wrote:
> 
>> I think the problem is from the SYSSRC make paremeter which is set to
>> skins/default/usr/src/linux, which seems to be invalid.
> 
> Where did you get the "skins" part of that? It isn't in what I posted.

Please take a deeper look at your first post... It is in your SYSSRC make
parameter.

> 
>> Maybe you can check to your environment for the variable KBUILD_OUTPUT
if
>> i remember correctly.
> 
> I seem not to have one.

Sorry, the variable is KERNEL_DIR.
Can you please post emerge --info and the full output from emerge
nvidia-drivers ?

> 
> Maybe the problem is in "CROSS_COMPILE=x86_64-pc-linux-gnu-", which seems

> incomplete.

No problem with this one as this is prefix for gcc,ar,etc... (for example
x86_64-pc-linux-gnu-gcc)

HTH.

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On Tuesday 21 April 2009 16:23:34 Xavier Parizet wrote:
> On Tue, 21 Apr 2009 16:07:02 +0100, Peter Humphrey
>
> <peter@humphrey.ukfsn.org> wrote:
> > On Tuesday 21 April 2009 10:56:25 Xavier Parizet wrote:
> >> I think the problem is from the SYSSRC make paremeter which is set to
> >> skins/default/usr/src/linux, which seems to be invalid.
> >
> > Where did you get the "skins" part of that? It isn't in what I posted.
>
> Please take a deeper look at your first post... It is in your SYSSRC make
> parameter.

I've read the post backwards and forwards, and I've had kmail search 
case-insensitively for "skin", and it isn't there. It wasn't there when I 
sent it, anyway, and grep says it isn't in the files I've attached this 
time either.

> Can you please post emerge --info and the full output from emerge
> nvidia-drivers ?

Attached. Also:

$ uname -r
2.6.29-gentoo-r1

$ ls -l /usr/src/linux
lrwxrwxrwx 1 root root 22 2009-04-05 09:15 /usr/src/linux -> 
linux-2.6.29-gentoo-r1

Thanks for your time.

-- 
Rgds
Peter

[-- Attachment #2: emerge.out --]
[-- Type: text/x-diff, Size: 4359 bytes --]

$ sudo emerge nvidia-drivers
Calculating dependencies ... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-180.51
 * NVIDIA-Linux-x86_64-180.51-pkg2.run RMD160 SHA1 SHA256 size ;-) ...               [ ok ]
 * checking ebuild checksums ;-) ...                                                 [ ok ]
 * checking auxfile checksums ;-) ...                                                [ ok ]
 * checking miscfile checksums ;-) ...                                               [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/2.6.29-gentoo-r1/build
 * Found sources for kernel version:
 *     2.6.29-gentoo-r1
 * Checking for MTRR support ...                                                      [ ok ]
 * Checking for Paravirtualized guest support ...
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-180.51-pkg2.run to /tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2
 * Applying NVIDIA_glx-defines.patch ...                                              [ ok ]
 * Applying NVIDIA_glx-glheader.patch ...                                             [ ok ]
 * Applying NVIDIA_i2c-hwmon.patch ...                                                [ ok ]
 * Converting NVIDIA-Linux-x86_64-180.51-pkg2/usr/src/nv/Makefile.kbuild to use M= instead of SUBDIRS= ...                                                                        [ ok ]
>>> Source unpacked in /tmp/portage/x11-drivers/nvidia-drivers-180.51/work
>>> Compiling source in /tmp/portage/x11-drivers/nvidia-drivers-180.51/work/NVIDIA-Linux-x86_64-180.51-pkg2 ...
 * Preparing nvidia module
make -j3 -s HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.29-gentoo-r1/build HOST_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
 *
 * ERROR: x11-drivers/nvidia-drivers-180.51 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3792:  Called linux-mod_src_compile
 *             environment, line 2799:  Called die
 * The specific snippet of code:
 *               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}";
 *  The die message:
 *   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=  IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux           SYSOUT=/lib/modules/2.6.29-gentoo-r1/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/log/portage/x11-drivers:nvidia-drivers-180.51:20090421-232642.log'.
 * The ebuild environment file is located at '/tmp/portage/x11-drivers/nvidia-drivers-180.51/temp/environment'.
 *

>>> Failed to emerge x11-drivers/nvidia-drivers-180.51, Log file:

>>>  '/var/log/portage/x11-drivers:nvidia-drivers-180.51:20090421-232642.log'

[-- Attachment #3: emerge.info --]
[-- Type: text/plain, Size: 3703 bytes --]

Portage 2.2_rc31 (default/linux/amd64/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.29-gentoo-r1 x86_64)
=================================================================
System uname: Linux-2.6.29-gentoo-r1-x86_64-AMD_Opteron-tm-_Processor_246-with-glibc2.2.5
Timestamp of tree: Tue, 21 Apr 2009 08:45:02 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p39
dev-java/java-config: 2.1.7
dev-lang/python:     2.4.4-r14, 2.5.4-r2
dev-python/pycrypto: 2.0.1-r8
dev-util/ccache:     2.4-r7
dev-util/cmake:      2.6.2-r1
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.13, 2.63
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -mtune=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/init.d /etc/pam.d /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-march=native -mtune=native -O2 -pipe"
DISTDIR="/usr-bits/distfiles"
EMERGE_DEFAULT_OPTS="--with-bdeps y --nospinner"
FEATURES="buildpkg ccache distlocks fixpackages parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk 	http://ftp.easynet.nl/mirror/gentoo 	http://distfiles.gentoo.org"
LANG="en_GB.UTF-8"
LC_ALL="en_GB.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="en_GB"
MAKEOPTS="-j3 -s"
PKGDIR="/usr/portage/packages"
PORTAGE_COMPRESS=""
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/layman/webapps-experimental"
SYNC="rsync://serv.ethnet/gentoo-portage"
USE="X acl acpi alsa amd64 arts berkdb bzip2 cdr cli cracklib crypt cups dbus dri dvd dvdr encode exif fam ffmpeg flac fortran gdbm gif gpm gtk hal iconv ipv6 javascript jpeg jpeg2k kde lame logitech-mouse logrotate mad midi mmx mng mp3 mpeg mudflap multilib ncurses nls nptl nptlonly nvidia ogg opengl openmp pam pcre pdf perl png pppd python qt3 readline reflection session smp spell spl sse sse2 ssl subversion svg sysfs tcpd tiff truetype unicode usb vcd vorbis wmf xml xorg xulrunner xvmc zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CAMERAS="fuji" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="nv"
Unset:  CPPFLAGS, CTARGET, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Paul Hartman]

On Tue, Apr 21, 2009 at 6:34 PM, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> I've read the post backwards and forwards, and I've had kmail search
> case-insensitively for "skin", and it isn't there. It wasn't there when I
> sent it, anyway, and grep says it isn't in the files I've attached this
> time either.

As a third party in this thread I can confirm your original post has:

SYSSRC=/usr/src/linux

no "skins"

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Dale]

Paul Hartman wrote:
> On Tue, Apr 21, 2009 at 6:34 PM, Peter Humphrey
> <peter@humphrey.ukfsn.org> wrote:
>   
>> I've read the post backwards and forwards, and I've had kmail search
>> case-insensitively for "skin", and it isn't there. It wasn't there when I
>> sent it, anyway, and grep says it isn't in the files I've attached this
>> time either.
>>     
>
> As a third party in this thread I can confirm your original post has:
>
> SYSSRC=/usr/src/linux
>
> no "skins"
>
>
>   

Same here.  Word find and my eyes found no mention of skins.  Since I'm
curious, how did that get there?  Two emails merge somewhere or something.

Dale

:-)  :-)

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Wed, 22 Apr 2009 00:34:34 +0100, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> On Tuesday 21 April 2009 16:23:34 Xavier Parizet wrote:
>> On Tue, 21 Apr 2009 16:07:02 +0100, Peter Humphrey
>>
>> <peter@humphrey.ukfsn.org> wrote:
>> > On Tuesday 21 April 2009 10:56:25 Xavier Parizet wrote:
>> >> I think the problem is from the SYSSRC make paremeter which is set to
>> >> skins/default/usr/src/linux, which seems to be invalid.
>> >
>> > Where did you get the "skins" part of that? It isn't in what I posted.
>>
>> Please take a deeper look at your first post... It is in your SYSSRC
make
>> parameter.
> 
> I've read the post backwards and forwards, and I've had kmail search 
> case-insensitively for "skin", and it isn't there. It wasn't there when I

> sent it, anyway, and grep says it isn't in the files I've attached this 
> time either.

In fact you're right, it seems that my webmail (Roundcube) add the
skins/default part i saw earlier in your first post... Looking at the mail
source and there is no skins/default part.
Apologize :)

>> Can you please post emerge --info and the full output from emerge
>> nvidia-drivers ?
> 
> Attached. Also:
> 
> $ uname -r
> 2.6.29-gentoo-r1
> 
> $ ls -l /usr/src/linux
> lrwxrwxrwx 1 root root 22 2009-04-05 09:15 /usr/src/linux -> 
> linux-2.6.29-gentoo-r1
> 
> Thanks for your time.

Do you run make prepare in the kernel source tree with your kernel
configured ?

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Wednesday 22 April 2009 08:49:19 Xavier Parizet wrote:
> In fact you're right, it seems that my webmail (Roundcube) add the
> skins/default part i saw earlier in your first post... Looking at the
> mail source and there is no skins/default part.
> Apologize :)

Thanks. You had me worried for a while! It's an odd problem that caused it 
though.

> Do you run make prepare in the kernel source tree with your kernel
> configured ?

No, when going up a revision level I just copy in the previous .config and 
make oldconfig to check that no new variables have been introduced; then I 
make && make modules_install.

-- 
Rgds
Peter

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Wed, 22 Apr 2009 00:34:34 +0100, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> On Tuesday 21 April 2009 16:23:34 Xavier Parizet wrote:
>> On Tue, 21 Apr 2009 16:07:02 +0100, Peter Humphrey
>>
>> <peter@humphrey.ukfsn.org> wrote:
>> > On Tuesday 21 April 2009 10:56:25 Xavier Parizet wrote:
>> >> I think the problem is from the SYSSRC make paremeter which is set to
>> >> skins/default/usr/src/linux, which seems to be invalid.
>> >
>> > Where did you get the "skins" part of that? It isn't in what I posted.
>>
>> Please take a deeper look at your first post... It is in your SYSSRC
make
>> parameter.
> 
> I've read the post backwards and forwards, and I've had kmail search 
> case-insensitively for "skin", and it isn't there. It wasn't there when I

> sent it, anyway, and grep says it isn't in the files I've attached this 
> time either.
> 
>> Can you please post emerge --info and the full output from emerge
>> nvidia-drivers ?
> 
> Attached. Also:
> 
> $ uname -r
> 2.6.29-gentoo-r1
> 
> $ ls -l /usr/src/linux
> lrwxrwxrwx 1 root root 22 2009-04-05 09:15 /usr/src/linux -> 
> linux-2.6.29-gentoo-r1
> 
> Thanks for your time.

Can you repost emerge output using MAKEOPTS="-j1" to see what make command
is launched.
Try also to run make prepare in your kernel source tree before.

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Wednesday 22 April 2009 11:30:27 Xavier Parizet wrote:

> Can you repost emerge output using MAKEOPTS="-j1" to see what make
> command is launched.
> Try also to run make prepare in your kernel source tree before.

# cd /usr/src/linux
# make prepare
# MAKEOPTS="-j1" emerge nvidia-drivers

This time it compiled just fine.

Things are getting complicated now, so I propose to leave well alone.

Thanks for the suggestions - I can't say which was effective, as I was tired 
and didn't think the steps through properly.

-- 
Rgds
Peter

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Alan McKinnon]

On Wednesday 22 April 2009 23:45:19 Peter Humphrey wrote:
> On Wednesday 22 April 2009 11:30:27 Xavier Parizet wrote:
> > Can you repost emerge output using MAKEOPTS="-j1" to see what make
> > command is launched.
> > Try also to run make prepare in your kernel source tree before.
>
> # cd /usr/src/linux
> # make prepare
> # MAKEOPTS="-j1" emerge nvidia-drivers
>
> This time it compiled just fine.

I reckon the maintainer of the nvidia-driver ebuild would be *very* interested 
in this. "-j" is well known for causing weird faults.

I recommend submitting a bug along with all build logs etc

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Xavier Parizet]

On Thu, 23 Apr 2009 00:04:13 +0200, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:
> On Wednesday 22 April 2009 23:45:19 Peter Humphrey wrote:
>> On Wednesday 22 April 2009 11:30:27 Xavier Parizet wrote:
>> > Can you repost emerge output using MAKEOPTS="-j1" to see what make
>> > command is launched.
>> > Try also to run make prepare in your kernel source tree before.
>>
>> # cd /usr/src/linux
>> # make prepare
>> # MAKEOPTS="-j1" emerge nvidia-drivers
>>
>> This time it compiled just fine.
> 
> I reckon the maintainer of the nvidia-driver ebuild would be *very*
> interested 
> in this. "-j" is well known for causing weird faults.
> 
> I recommend submitting a bug along with all build logs etc

I think the MAKEOPTS was not the problem, but only the make prepare... I
remember to see before that "sometimes", the kernel source tree is no more
up-to-date with the last kernel build, so when i see that problems, the
first thing to do is to make mrproper && make oldconfig && make prepare to
get a clean up-to-date kernel build tree.

Cheers.

-- 
      Xavier Parizet
YaGB :   http://gentooist.com
GPG  :    DC81 6FEE 6EBE FCE4 
1C18 202F E575 4A5D 036D 1408

Re: [gentoo-user] nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Thursday 23 April 2009 07:43:20 Xavier Parizet wrote:

> I think the MAKEOPTS was not the problem, but only the make prepare... I
> remember to see before that "sometimes", the kernel source tree is no
> more up-to-date with the last kernel build, so when i see that problems,
> the first thing to do is to make mrproper && make oldconfig && make
> prepare to get a clean up-to-date kernel build tree.

I don't like the sound of that; it's distinctly ominous. What can interfere 
with the kernel source tree after I've compiled a kernel, copied it to the 
boot partition, booted it and moved on to other things?

One or two packages install modules into the source tree, but at the moment 
I can only think of the one I was working on: nvidia-drivers. Or is it that 
compiling the kernel itself damages its own source configuration?

-- 
Rgds
Peter

[gentoo-user] Re: nvidia-drivers-180.51 on amd64

[walt]

Peter Humphrey wrote:
> On Thursday 23 April 2009 07:43:20 Xavier Parizet wrote:
>
>> I think the MAKEOPTS was not the problem, but only the make prepare... I
>> remember to see before that "sometimes", the kernel source tree is no
>> more up-to-date with the last kernel build, so when i see that problems,
>> the first thing to do is to make mrproper&&  make oldconfig&&  make
>> prepare to get a clean up-to-date kernel build tree.
>
> I don't like the sound of that; it's distinctly ominous. What can interfere
> with the kernel source tree after I've compiled a kernel, copied it to the
> boot partition, booted it and moved on to other things?
>
> One or two packages install modules into the source tree, but at the moment
> I can only think of the one I was working on: nvidia-drivers. Or is it that
> compiling the kernel itself damages its own source configuration?

Whenever I have the same problem it's because I've done a 'make clean' or
equivalent in /usr/src/linux, or more likely because a newer version of
the kernel sources has been installed but I haven't yet built the newer
kernel.

It's possible that both the kernel sources and nvidia-drivers were
updated about the same time, and when that happens the nvidia-drivers
will be compiled immediately whereas the new kernel won't be compiled
until you decide to go do it yourself.  (Meanwhile, nvidia-drivers has
crapped out.)

Re: [gentoo-user] Re: nvidia-drivers-180.51 on amd64

[Peter Humphrey]

On Friday 24 April 2009 01:59:59 walt wrote:

> Whenever I have the same problem it's because I've done a 'make clean' or
> equivalent in /usr/src/linux, or more likely because a newer version of
> the kernel sources has been installed but I haven't yet built the newer
> kernel.
>
> It's possible that both the kernel sources and nvidia-drivers were
> updated about the same time, and when that happens the nvidia-drivers
> will be compiled immediately whereas the new kernel won't be compiled
> until you decide to go do it yourself.  (Meanwhile, nvidia-drivers has
> crapped out.)

Yes, but those don't apply here. I had, as I said, a current kernel source 
directory (by which I mean I had compiled the currently running kernel in 
it) and was installing the latest version of nvidia. I hadn't done anything 
in the source tree since compiling the kernel, so it should have Just 
Worked.

-- 
Rgds
Peter