On Thu, Dec 17, 2009 at 10:26:39PM -0300, Daniel Bareiro wrote: > > Well, the kernel build does check what your current config is, and > > based on that, asks you some new questions. One way I get around this > > is: > > > > cd <kernel-build-directory> > > cp /boot/config-$(uname -r) .config > > make menuconfig # choose the options you want. > > Run make-kpkg to build my kernel deb. > > > > The make menuconfig step refreshes your config, so that you can skip > > the "interrogation" step. > > These steps are similar to which I'm doing, although not to the Debian > way: > > # cd /usr/src/linux-2.6.32 > # cp /boot/config-`uname -r` ./.config > # make ARCH=x86_64 menuconfig > # make > > The "interrogation" step comes when doing "make". > > But it seems that it is obtaining some things of the configuration in > /boot/, because in the questions I see (without form to be able to > modify) that the family is Pentium-Pro (M686) and in > /usr/src/linux/.config I have: > > CONFIG_64BIT=y > # CONFIG_X86_32 is not set > CONFIG_X86_64=y > CONFIG_X86=y
Well, then did you try using make menuconfig? I would guess that that
would "refresh" your .config, thereby skipping the interrogation. In
my case:
[ku...@bluemoon ~/Software/Kernel/linux-git master] make
[snip]
scripts/kconfig/conf -s arch/x86/Kconfig
*
* Restart config...
*
*
* RCU Subsystem
*
RCU Implementation
> 1. Tree-based hierarchical RCU (TREE_RCU)
2. Preemptable tree-based hierarchical RCU (TREE_PREEMPT_RCU) (NEW)
choice[1-2]:
I now hit Ctrl+C. Next, I do
make menuconfig
I just select Exit. When asked if I can save the configuration file, I say yes.
Now, observe:
[ku...@bluemoon ~/Software/Kernel/linux-git master] make
scripts/kconfig/conf -s arch/x86/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
...
The interrogation step was skipped.
Hope this helps.
Kumar
--
> Where in the US is Linus?
He was in the "Promise Land".
-- David S. Miller <[email protected]>
signature.asc
Description: Digital signature
