Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 109884 - emerge fails on svgalib-1-9-21-r1 (during "emerge --update --deep -newuse world")
Summary: emerge fails on svgalib-1-9-21-r1 (during "emerge --update --deep -newuse wor...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-19 21:42 UTC by John Poole
Modified: 2005-10-22 10:52 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Poole 2005-10-19 21:42:24 UTC
I was performing a full "emerge --update --deep -newuse world" (been over a year
since I tried this) and it dies on svgalib-1-9-21-r1.  

I tried the recommended approach from Bug 106232
"svgalib-1.9.21-r1 doesn't build if kernel support for modules not enabled
(2.6.9-gentoo-r13 anyway)" which was "USE=no-helper emerge svgalib" and had the
same problem.  Here is the output from "USE=no-helper emerge svgalib
1>emerge_svgalib.txt 2>emerge_svgalib_err.txt":
.
emerge_svgalib.txt:
vvvvvvvvvvvvvvv
Calculating dependencies   [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 sources for kernel version:
 [32;01m*[0m     2.6.13-gentoo-r3

 [31;01m*[0m getfilevar requires 2 variables, with the second a valid file.
 [31;01m*[0m    getfilevar <VARIABLE> <CONFIGFILE>
 [31;01m*[0m Could not find a usable .config in the kernel source directory.
 [31;01m*[0m Please ensure that /usr/src/linux points to a configured set of
Linux sources.
 [31;01m*[0m If you are using KBUILD_OUTPUT, please set the environment var so
that
 [31;01m*[0m it points to the necessary object directory so that it might find
.config.
  ...done!
>>> emerge (1 of 1) media-libs/svgalib-1.9.21-r1 to /
>>> md5 files   ;-) svgalib-1.9.19-r3.ebuild
>>> md5 files   ;-) svgalib-1.9.21-r1.ebuild
>>> md5 files   ;-) files/digest-svgalib-1.9.19-r3
>>> md5 files   ;-) files/digest-svgalib-1.9.21-r1
>>> md5 files   ;-) files/svgalib-1.9.21-linux2.6.patch
>>> md5 files   ;-) files/svgalib.udev.rules.d
>>> md5 files   ;-) files/svgalib.devfs
>>> md5 files   ;-) files/svgalib-1.9.19-gentoo.patch
>>> md5 files   ;-) files/svgalib-1.9.19-devfs.patch
>>> md5 files   ;-) files/svgalib-1.9.21-gentoo.patch
>>> md5 files   ;-) files/svgalib-1.9.19-pci-get-class.patch
>>> md5 files   ;-) files/svgalib-1.9.18-lrmi-gentoo-cflags.patch
>>> md5 files   ;-) files/svgalib.udev.perms.d
>>> md5 files   ;-) files/svgalib-1.9.19-pic.patch
>>> md5 files   ;-) files/svgalib-1.9.19-dont-touch-ld.conf.patch
>>> md5 files   ;-) files/svgalib-1.9.19-linux2.6.patch
>>> md5 files   ;-) files/svgalib-1.9.18-utils-include.patch
>>> md5 src_uri ;-) svgalib-1.9.21.tar.gz
^^^^^^^^^^^^^^^^
.
emerge_svgalib_err.txt:
vvvvvvvvvvvvvvv
!!! ERROR: media-libs/svgalib-1.9.21-r1 failed.
!!! Function linux-info_pkg_setup, Line 526, Exitcode 1
!!! Unable to calculate Linux Kernel version
!!! If you need support, post the topmost build error, NOT this status message.
^^^^^^^^^^^^^^^^
.


Reproducible: Always
Steps to Reproduce:
1. emerge svgalib
2.
3.

Actual Results:  
see output for 1> and 2> files above

Expected Results:  
build

I'm not familiar with the Severity ratings.  Basically, I'm gated from my
upgrade and I would classify this as "Critical" for me, but don't want to send
off alarms.  I'd like to complete my upgrade and would appreciate any suggested
work-arounds.  Can I exclude svgalib-1-9-21-r1, or is this going to affect my
newly build KDE environment?

Thank you!
Comment 1 John Poole 2005-10-19 22:00:56 UTC
Yup, I'm hosed insofar as my ability to start KDE now fails.  My normal "startx"
as a nonroot user results in the following error output:
vvvvvvvvvvvvvv

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.5-gentoo-r1 i686 [ELF] 
Current Operating System: Linux daphne 2.6.5-gentoo-r1 #3 SMP Thu May 27
21:57:32 UTC 2004 i686
Build Date: 16 October 2005
	Before reporting problems, check http://wiki.X.Org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 19 21:56:19 2005
(==) Using config file: "/etc/X11/XF86Config"
Using vt 7

(EE) Failed to load module "speedo" (module does not exist, 0)
Error: API mismatch: the NVIDIA kernel module is version 1.0.4480, but
this X module is version 1.0.6629. Please be sure that your kernel
module and all NVIDIA driver files have the same driver version.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0):  *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
	 at http://wiki.X.Org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"

      after 0 requests (0 known processed) with 0 events remaining.
^^^^^^^^^^^^^^^^^^^^^
Comment 2 Sophie Hamilton 2005-10-20 16:36:06 UTC
I'm not a dev, but as far as your X.org error goes, try "emerge nvidia-kernel
nvidia-glx", and then try startx again. That ought to fix the second problem.
Comment 3 Sophie Hamilton 2005-10-20 16:39:33 UTC
Oh, and unless you're doing specific types of development, you don't want to use
"USE=no-helper" as svgalib won't work properly that way. It isn't the source of
your problem, but this is just a heads-up.
Comment 4 John Poole 2005-10-20 22:43:56 UTC
Thank you, Ciaron.  I tried your suggestion and found I ran into the same
problem.  Looks it's a where's-the-config file issue and not necessarily related
to a particular build.  Here's the output I received when trying:
vvvvvvvvvvvvv
emerge nvidia-kernel nvidia-glx

 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.13-gentoo-r3

 * getfilevar requires 2 variables, with the second a valid file.
 *    getfilevar <VARIABLE> <CONFIGFILE>
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.

!!! ERROR: media-video/nvidia-kernel-1.0.6629-r4 failed.
!!! Function linux-info_pkg_setup, Line 526, Exitcode 1
!!! Unable to calculate Linux Kernel version
!!! If you need support, post the topmost build error, NOT this status message.
^^^^^^^^^^^^
Comment 5 John Poole 2005-10-20 22:54:43 UTC
It appears that I'm missing a ".config" file in linux-2.6.13-gentoo-r3:
vvvvvvvv
daphne src # pwd       
/usr/src
daphne src # find . -name '\.config'
./linux-2.6.11-gentoo-r9/.config
./linux-2.6.5-gentoo-r1/.config
daphne src # ls
linux                   linux-2.6.13-gentoo-r3  linux-2.6.7-gentoo-r11
linux-2.6.11-gentoo-r9  linux-2.6.5-gentoo-r1
daphne src # 
^^^^^^^^^
.
I don't recall any problems when I installed linux-2.6.13-gentoo-r3 back in June
(?).  Looks like I either have to recreate a config file/reinstall
linux-2.6.13-gentoo-r3.
Comment 6 John Poole 2005-10-21 01:21:56 UTC
Turned out that my kernel was updated and that a configuration was necessary. 
After I created the .config file, my emerge of svgalib was successful.
So the gate is removed.
.
Suggestion: if the kernel is being updated, shouldn't there be some sort of
mechanism that prevents other programs from being emerged until after the
configuration is performed?
.
Not sure what status to set this to, so am leaving as NEW so someone in the know
can recognize the problem I encountered and determine what might be implmented
to spare others from being taken to this stopping point.
Comment 7 Sophie Hamilton 2005-10-21 12:44:18 UTC
If you're using a 2.6.x kernel that exports its configuration via
/proc/config.gz , the easiest way to get the .config file is:

$ gzcat /proc/config.gz > /usr/src/linux/.config

That will create the .config file with the exact configuration that your running
kernel is using. The .config file is used during compilation of the kernel to
work out what options to compile, and it's also used by kernel module ebuilds
(such as the nvidia and svgalib ebuilds) to determine if you have the necessary
code in your kernel for the ebuilds to work. If the .config file is different
from what's actually compiled in, you could run into problems, so reconfiguring
is best done only immediately before recompiling the kernel.

Having said that, if nvidia and svgalib are working, there's probably no
problem. However, I'd advise that you run the above command just to make sure
you've got the right contents in the .config file.
Comment 8 Jakub Moc (RETIRED) gentoo-dev 2005-10-22 10:52:39 UTC
This bug is invalid, you need a configured kernel to emerge svgalib (and
existing /usr/src/linux symlink to the currently used kernel version).