Hi, Sven. On Friday, 18 December 2009 09:15:43 +0100, Sven Joachim wrote: > > I am trying to compile Linux 2.6.32 with the source code of > > kernel.org. Kernel that I'm using at the moment is 2.6.26-2-686 of > > the Debian GNU/Linux repositories. > > > > In order to generate the configuration, I've copied the file > > corresponding to this kernel to the directory of sources, > > /usr/src/linux, and I've executed make menuconfig: > > > > --------------------------------------------------------------------- > > # cd /usr/src/linux-2.6.32 > > # cp /boot/config-`uname -r` ./.config > > > > # make ARCH=x86_64 menuconfig > > --------------------------------------------------------------------- > It would be better to start with the configuration of Debian's -amd64 > images if you want to use a 64-bit kernel, or even install and boot > the 2.6.26-2-amd64 kernel. I was trying installing and booting 2.6.26-2-amd64 kernel and then compiling 2.6.32 kernel of the traditional way: # cd /usr/src/linux-2.6.32 # cp /boot/config-`uname -r` ./.config # make menuconfig # make In this case I didn't use the ARCH=x86_64 variable and after to execute 'make menuselect' to select the configuration parameters, when invoking 'make', this worked without doing any type of question. Could this be due to I booted previously with amd64 kernel? > > But when I execute 'make', restart config becomes and I'm > > interrogated on some details of the configuration: > > > > --------------------------------------------------------------------- > > antares:/usr/src/linux# make > > HOSTLD scripts/kconfig/conf > > scripts/kconfig/conf -s arch/x86/Kconfig > > * > > * Restart config... > > * > > * > > * RCU Subsystem > > * > > RCU Implementation > >> 1. Tree-based hierarchical RCU (TREE_RCU) > > choice[1]: 1 > > Enable tracing for RCU (RCU_TRACE) [N/y/?] n > > Tree-based hierarchical RCU fanout value (RCU_FANOUT) [32] (NEW) > > --------------------------------------------------------------------- > > > > Something similar happens when compiling using the Debian way. > That's because there are numerous changes between 2.6.26 and 2.6.32, > so your old configuration cannot be used as-is. > > You may want to run "make ARCH=x86_64 menuconfig" first, so that the > defaults are used. Otherwise you will have to answer literally > thousands of questions. I assume that it must have differences between both kernels versions; for that reason, as I've mentioned in another mail of this thread, after to have copied the file, I followed a similar procedure to which mentioned above, but with the ARCH=x86_64 variable: # cd /usr/src/linux-2.6.32 # cp /boot/config-`uname -r` ./.config # make ARCH=x86_64 menuconfig # make But in spite of to have used 'make menuconfig', 'make' did 'restart config' beginning to do questions to me. Also I tried what Kumer suggested to me of cancel with Ctrl+C when initiating the questions and to execute 'make menuconfig' again, but this only works in the case of not using ARCH=x86_64 with 'make menuconfig' in the second time that it is invoked. But when not using this variable, the processor family returns to be like Pentium Pro and in the .config file I get: # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y I tried selecting in the ncurses menu the option "Opteron/Athlon64/Hammer/K8" for the processor family, but even so I don't see changes in the values of the variables that I've indicated above. Thanks for your reply. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Lenny - Linux user #188.598
Attachment:
signature.asc
Description: Digital signature