Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 102514 - Problem of emerging svgalib when updating system
Summary: Problem of emerging svgalib when updating system
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-14 09:49 UTC by Vasudeva Martin
Modified: 2005-08-14 12:17 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 Vasudeva Martin 2005-08-14 09:49:17 UTC
When i update with emerge -uDN system I get the following error message.
<emerge-output>
>>> emerge (9 of 44) media-libs/svgalib-1.9.21 to /
>>> md5 files   ;-) svgalib-1.9.19-r3.ebuild
>>> md5 files   ;-) svgalib-1.9.21.ebuild
>>> md5 files   ;-) files/digest-svgalib-1.9.19-r3
>>> 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/digest-svgalib-1.9.21
>>> 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
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.12-gentoo-r8

 * 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-libs/svgalib-1.9.21 failed.
!!! Function linux-info_pkg_setup, Line 521, Exitcode 1
!!! Unable to calculate Linux Kernel version
!!! If you need support, post the topmost build error, NOT this status message.
</emerge-output>

The problem is explained in the following line:
 * Could not find a usable .config in the kernel source directory.
That's no wounder, because after updating the kernel there is no ".config" file
in /usr/src/linux.


Reproducible: Always
Steps to Reproduce:
1. emerge -uDN system
But I think it's only reproducable if your kernel has been updated. Because in
this case the Kernel source in /usr/src/linux contains no ".config"


Actual Results:  
The error message you can see in Details

Expected Results:  
Install properly. For this aim it would be a good thing that svgalib install
routine scans all /usr/src/linux-* for a ".config" if there is no ".config" file
in /usr/src/linux.
 

After 
1. copying the ".config"-File from my old kernel to my new updated kernel
version where the /usr/src/linux symlink pointed to and 
2. do a "make menuconfig" with exiting and saving the configuration and a 
3. "make bzImage modules modules_install install"
I could emerge svgalib without any errors.
Maybe steps 2 and 3 are not necessary to emerge svgalib but I think if there is
a new kernel normally you want to use it.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-08-14 10:14:22 UTC
You need a configured kernel for this to work, as the error message says. Sorry,
nothing we could do about it. 
Comment 2 Vasudeva Martin 2005-08-14 11:47:02 UTC
So could you explain me why it is not possible to scan for an ".config" file in
"/usr/src/linux-*" ? 
Another maybe the better solution would be if the install-routine of the kernel
which sets the /usr/src/linux symlink to the new kernel version, automatically
copy the ".config" file from the old kernel directory to the new one. 
The big problem of this bug is that it prevents you from updating your system
with only an "emerge -uDN system". 
This should not be an accepted state.
Because compiling often takes a long time, it's a good thing if you can do
something like a "emerge foo_takes_a_long_time; halt" after work.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-08-14 12:02:05 UTC
(In reply to comment #2)
> So could you explain me why it is not possible to scan for an ".config" file in
> "/usr/src/linux-*" ? 

Huh? And if you have like 10 configured kernels, then pick a random one? You are
not serious, are you? :)
Comment 4 Vasudeva Martin 2005-08-14 12:17:41 UTC
(In reply to comment #3)
Ok there might be a problem if you have more Kernels of the same Version, but if
not you could choose the one with the highest version number.
But what is with my other suggestion which I would prefer because I think it's
the better solution. When the kernel is updated the install-routine of the
Kernel sources could easily copy the ".config" file from the "/usr/src/linux"
symlink to the new kernel directory.