First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 207895
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Genkernel Maintainers <genkernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Patrik Wenger <paddor@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 207895 depends on: Show dependency tree
Bug 207895 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-01-28 13:57 0000 
in /etc/genkernel.conf I can set OLDCONFIG to "yes" and "no" and even unset,
"make oldconfig" is always run. I always get this output:

----------- BEGIN -----------
paddor@pantoo linux $ sudo genkernel --kernname=paddor.1 all
* Gentoo Linux Genkernel; Version 3.4.9
* Running with options: --kernname=paddor.1 all

* Linux Kernel 2.6.24-gentoo for x86_64...
* config: Using config from /etc/kernels/kernel-config-x86_64-2.6.24-gentoo
*         Previous config backed up to .config.bak
*         >> Running oldconfig...
* kernel: >> Cleaning...
----------- END (cutted) ---------

Also, it takes always the config of /etc/kernels/, although there exists an
.config. This will just be backed up to .config.bak.
So I have to specify the edited config with --kernel-config or "on the fly"
with MENUCONFIG="yes" or --menuconfig so menuconfig is invoked and I can set my
settings.

------- Comment #1 From Andrew Gaffney 2008-02-03 03:37:48 0000 ------- 
It looks like the logic for handling OLDCONFIG is a bit...weird. Looking at the
code, if CLEAN is set to yes, oldconfig is executed regardless of what
OLDCONFIG is set to.

The behavior you mention about using the previous config is "normal" for a
kernel version that you've compiled before. If you want to use a different
kconfig file, use the --kernel-config=<foo> option.

------- Comment #2 From Andrew Gaffney 2008-02-03 06:14:33 0000 ------- 
I've committed a fix for this in SVN. However, disabling OLDCONFIG will not get
you the results you want. That comment in genkernel.conf that said setting
OLDCONFIG="yes" would disable the fetching of the kconfig from /etc/kernels/
was outdated. There is no code to do that.

------- Comment #3 From Chris Gianelloni (RETIRED) 2008-02-14 04:32:39 0000 ------- 
I just released genkernel 3.4.10_pre1, which has this fix included.  Feel free
to REOPEN this bug or make a comment if it is not resolved.
First Last Prev Next    No search results available      Search page      Enter new bug