Getting this when trying to "make bzImage"...

trist007 · 10-14-2012, 09:31 PM

Code:

make[1]: *** No rule to make target `kernel/+', needed by `kernel/built-in.o'.  Stop.

I just downloaded the kernel source from kernel.org. Then I copied my /boot/config to the kernel src tree .config. Then ran make menuconfig, make 2 tweaks. Then ran "make bzImage" and then got that error from make.

What does it mean exactly?

-Tristan

Rupadhya · 10-14-2012, 11:34 PM

I haven't worked with Slackware in awhile so I don't know if you will have other issues, but this is what I do on Fedora.

Code:

mkdir ~/build                                # A directory where your build will be built.
make O=/home/name/build/kernel mrproper      #  Replace name with your username.  This will clean up any .o from an old build
copy your config file to .config in your source directory
make O=/home/name/build/kernel oldconfig     # This parses your old config and updates it with new options.
make O=/home/name/build/kernel menuconfig    # Make your 2 tweaks
rm .config in the source directory           # I think your build will sense this and not allow you to build if you don't
make O=/home/name/build/kernel               # This is the build.  It takes awhile to execute
sudo make O=/home/name/build/kernel modules_install install    # This copies your bzImage to the /boot directory
                                                               # Sets up some symbolic links and updates the grub.cfg

Reboot and test.. If you have other problems, please reply to this thread.

- Raj Upadhyaya

trist007 · 10-15-2012, 08:51 AM

Nice, I'll try that.

So the "make" will do both make bzImage and modules correct? At least that's what it looks like in the Makefile.

-Tristan

Rupadhya · 10-15-2012, 09:40 AM

Yes. It takes a while and it compiles and links all the modules necessary to make the kernel, and it links it together to make bzImage.
- Raj

trist007 · 10-15-2012, 09:47 AM

Thanks.

-Tristan

business_kid · 10-15-2012, 10:03 AM

Just run make. make help if you want to inform yourself.

Be sure to be sitting in the kernel top source. I never bother with a build directory - too much messing, and the kernel keeps the source clean anyhow.