Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 194752 - genkernel --kernel-config man page error
Summary: genkernel --kernel-config man page error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: genkernel (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Genkernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-04 22:42 UTC by Tommaso Visconti
Modified: 2008-01-12 00:51 UTC (History)
1 user (show)

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 Tommaso Visconti 2007-10-04 22:42:22 UTC
Hi, from genkernel man page:

--kernel-config=<file>
              This specifies a kernel configuration file to use for compilation; by default .config in the kernel source tree is used.

but if the kernel was still correctly compilated with genkernel (most of the times), the config file used is /etc/kernels/kernel-config-[version] and not .config in the kernel source tree as we can see launching "genkernel all". In my case:

* config: Using config from /etc/kernels/kernel-config-x86-2.6.22-gentoo-r8-mactel


Reproducible: Always
Comment 1 Andrew Gaffney (RETIRED) gentoo-dev 2007-12-27 22:40:03 UTC
I've applied the following patch in SVN:

--- genkernel.8	(revision 574)
+++ genkernel.8	(working copy)
@@ -140,7 +140,8 @@
 .TP
 \fB\-\-kernel\-config=\fR<file>
 This specifies a kernel configuration file to use for compilation; by
-default .config in the kernel source tree is used.
+default genkernel uses the config from the previous build of the same kernel
+version or a default kernel config if there isn't a previous config.
 .PP
 .BR Low-Level \ Compilation \ Options
 .TP
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2008-01-12 00:51:16 UTC
This should be resolved in genkernel 3.4.9, which will be hitting the tree shortly.  If this is still an issue with that version, please REOPEN this bug (or comment, if you cannot REOPEN it).