On 2009-12-18 16:56 +0100, Daniel Bareiro wrote: > 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?
Not really, make menuconfig selects the defaults for options which did not exist in previous kernels. Note that it will use the architecture of the running kernel if you do not specify ARCH. > 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. If you are not running a 64-bit kernel, you have to specify ARCH=x86_64 for _all_ make invocations. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
