Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have downloaded the kernel 2.6.37 from I have tried to compile it but I get an error:

$ make menuconfig
scripts/kconfig/conf --silentoldconfig Kconfig
*** Configuration file ".config" not found!
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.

I have copied the actual kernel configuration to .config:

cp /boot/config-2.6.37-20110117 .config

I have executed make menuconfig another time but it compiles the full kernel without showing a menu. o_O I have compiled this kernel a few days without problems.

Any help? Thanks.

share|improve this question
So so that it's mentioned here, and it has nothing to do with compiling the Kernel, there's a Mainline Kernel PPA which does already contain 2.6.37. These are already compiled binary packages that you can just install. They come with all of the same caveats as compiling the kernel yourself. – Stefano Palazzo Jan 19 '11 at 13:29

I do this on a fairly regular basis. It's quite simple. I follow the "Old fashioned way" instructions. If you're not, read that from the beginning and make sure you have the right things installed. My steps are as follows:

  1. Download kernel, extract it, and cd into the resultant directory.
  2. Copy in the config from the running kernel:

    cp -vi /boot/config-`uname -r` .config
  3. Show the new config keys and set values (optional):

    make oldconfig
  4. Main config (if I need to change things, optional again):

    make menuconfig
  5. Compile and package:

    env CONCURRENCY_LEVEL=8 fakeroot make-kpkg --initrd kernel-image kernel-headers
share|improve this answer
The solution was so simply. I had defined one alias to "make" that interfered. – Juan Simón Jan 19 '11 at 14:18
up vote 0 down vote accepted

The error was an alias of make that I have defined in my .bashrc.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.