Possible bug in E-build file or somewhere. Basically it throws up a few errors when trying to patch before compiling, and dies. Reproducible: Always Steps to Reproduce: 1. emerge the file (I did with emerge -a world) Actual Results: Calculating world dependencies ...done! [ebuild NS ] media-video/nvidia-kernel-1.0.6629-r1 [ebuild U ] net-www/elinks-0.10_rc1 [0.10_pre2] [ebuild U ] sys-kernel/genkernel-3.1.0d [3.1.0c] Do you want me to merge these packages? [Yes/No] >>> emerge (1 of 3) media-video/nvidia-kernel-1.0.6629-r1 to / * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.9-gentoo-r6 * Checking for suitable kernel configuration options * Using KV_OBJ=ko * Checking for MTRR support ... [ ok ] >>> Unpacking source... bash: /usr/portage/distfiles/-.run: No such file or directory /usr/portage/media-video/nvidia-kernel/nvidia-kernel-1.0.6629-r1.ebuild: line 89: cd: /var/tmp/portage/nvidia-kernel-1.0.6629-r1/work/-/usr/src/nv: No such file or directory * Applying NVIDIA_kernel-1.0-6629-1155389.patch ... * Failed Patch: NVIDIA_kernel-1.0-6629-1155389.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/nvidia-kernel-1.0.6629-r1/temp/NVIDIA_kernel-1.0-6629-1155389.patch-3185.out !!! ERROR: media-video/nvidia-kernel-1.0.6629-r1 failed. !!! Function epatch, Line 402, Exitcode 0 !!! Failed Patch: NVIDIA_kernel-1.0-6629-1155389.patch! !!! If you need support, post the topmost build error, NOT this status message. Expected Results: Should compile and install. Portage 2.0.51-r8 (default-linux/x86/2004.2, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.8-gentoo-r8 i686) ================================================================= System uname: 2.6.8-gentoo-r8 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 1 2004, 19:05:55)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.4_p6, 1.6.3, 1.9.3, 1.5, 1.7.9 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.4.22 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -pipe " CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/fax /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/control /var/spool/fax/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -pipe " DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://localhost/pub/gentoo/ http://cudlug.cudenver.edu/gentoo/ http://mirror.datapipe.net/gentoo http://gentoo.ccccom.com http://gentoo.mirrors.pair.com/ http://gentoo.llarian.net/" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl alsa apm arts avi berkdb bitmap-fonts crypt cups encode foomaticdb fortran gdbm gif gnome gpm gtk gtk2 ipv6 jpeg kde libwww mad mikmod motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl spell ssl svga tcpd truetype xml2 xmms xv zlib"
Same here with 2.6.9-r10 and 2.6.9-r11 kernels
Same here... for some strange reasons ebuild does not detect architecture.... Emerging with USE="x86" emerge nvidia-kernel solve the problem. However user *must* not set architecture flag...
Ditto for gentoo-dev-sources-2.6.9-r9 and nvidia-kernel-1.0.6111-r3. USE="x86" emerge --deep nvidia-kernel fixes the problem here too.
emerging net-snmp with lm_sensors cause same problem - x86 unsupported arch :) Is BUG in last portage version 2.0.51-r3.
Temporarly solution add in your make.conf (USE variable). USE="x86 [....<your other flags>]"
throwing USE="x86" on the command line seems to fix THAT issue, but it still dies when it tries to build the module, complaining that the rivafb module conflicts and should be removed. Well I do not have a rivafb module loaded, and if it was compiled at all, it was compiled by genkernel. I just compiled my current kernel with genkernel's defaults. mars ~ # USE="x86" emerge -a world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild NS ] media-video/nvidia-kernel-1.0.6629-r1 [ebuild U ] net-www/elinks-0.10_rc1 [0.10_pre2] [ebuild U ] sys-kernel/genkernel-3.1.0d [3.1.0c] Do you want me to merge these packages? [Yes/No] >>> emerge (1 of 3) media-video/nvidia-kernel-1.0.6629-r1 to / >>> md5 src_uri ;-) NVIDIA-Linux-x86-1.0-6629-pkg1.run * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.9-gentoo-r6 * Checking for suitable kernel configuration options * Using KV_OBJ=ko * Checking for MTRR support ... [ ok ] >>> Unpacking source... Creating directory NVIDIA-Linux-x86-1.0-6629-pkg1 Verifying archive integrity... OK Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86 1.0-6629......................................................................................................................................................................................................... * Applying nv-shutup-warnings.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1155389.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1161283.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1162524.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1165235.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1171869.patch ... [ ok ] * Applying NVIDIA_kernel-1.0-6629-1175225.patch ... [ ok ] * Applying 2.6 kernel patches * Applying conftest_koutput_includes.patch ... [ ok ] * Applying nv-disable-preempt-on-smp_processor_id.patch ... [ ok ] * Converting NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/Makefile.kbuild to use M= instead of SUBDIRS= ... [ ok ] >>> Source unpacked. * Preparing nvidia module Your kernel was configured to include rivafb support! The rivafb driver conflicts with the NVIDIA driver, please reconfigure your kernel and *disable* rivafb support, then try installing the NVIDIA kernel module again. *** Failed rivafb sanity check. Bailing out! *** make[1]: *** [rivafb-sanity-check] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [module] Error 2
It's not about a loaded rivafb module, it's about rivafb included in your current kernel configuration! Check that "Device Drivers"->"Graphics support"->"nVidia Riva support" is disabled.
Works for me with sys-apps/portage-2.0.51-r8 (from the current sync)
*** Bug 75304 has been marked as a duplicate of this bug. ***
I believe this bug was INVALID to begin with and it's been years since the complaint. Resolving.
