no rule to make target kernel/bounds.c
Hello,
I must compile my kernel for my webcam driver. But after the command "make prepare", I've got that :
make[1]: *** No rule to make target `kernel/bounds.c', needed by `kernel/bounds.s'. Stop.
make: *** [prepare0] Error 2
so I've try sudo apt-get --reinstall install linux-headers-`uname -r` and I've installed the kernel source, but without any success...
It's the same error with other kernel version.
Can you help me please ?
$(uname -r) is 2.6.27-9-server
Re: no rule to make target kernel/bounds.c
Hi!
Installing the kernel sources using apt / aptitude / synaptic / whatsoever only puts the compressed source code into /usr/src. You need to uncompress the sources:
Code:
$ cd /usr/src
$ sudo tar -xvjf linux-source-$YOUR_VERSION_HERE.tar.bz2
Then just change into the new /usr/src/linux-source-$YOUR_VERSION_HERE directory and built your kernel like you used to :-)
So long
Re: no rule to make target kernel/bounds.c
Thank you. This helped me with the same problem.
Re: no rule to make target kernel/bounds.c
Sorry, I'm new in it, what does $YOUR_VERSION_HERE mean? Is it my kernel version?
Thanks.
Re: no rule to make target kernel/bounds.c
Sorry for my last reply. I installed linux-source and then I understood what you meant with $YOUR_VERSION_HERE.
Thanks!
Re: no rule to make target kernel/bounds.c
I have the same problem but my archive is uncompressed already ! But i still get the same message
***@***-laptop:~$ cd microdia
***@***-laptop:~/microdia$ sudo make
make -C /lib/modules/2.6.28-15-generic/build SUBDIRS= modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-15-generic'
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
make[2]: *** No rule to make target `kernel/bounds.c', needed by `kernel/bounds.s'. Stop.
make[1]: *** [prepare0] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'
make: *** [driver] Error 2
I'm trying to setup my built-in webcam on Lenovo 3000 N100 (Ubuntu 9.04)
I need help !!!!
Re: no rule to make target kernel/bounds.c
I have same problem, and installing linux-source didn't not help, this is a fresh ubuntu 9.04 installation and ran latest updates.
This command has also been used:
Code:
$sudo apt-get install build-essential linux-headers-$(uname -r)
I always get the following error:
Code:
kinnunen@Atom:~/Desktop/rtl8192u_linux_2.6.0006.1031.2008$ sudo make install
[sudo] password for kinnunen:
make[1]: Entering directory `/home/kinnunen/Desktop/rtl8192u_linux_2.6.0006.1031.2008/ieee80211'
make -C /lib/modules/2.6.28-15-generic/build M= CC=gcc modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.28-15-generic'
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
make[3]: *** No rule to make target `kernel/bounds.c', needed by `kernel/bounds.s'. Stop.
make[2]: *** [prepare0] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/kinnunen/Desktop/rtl8192u_linux_2.6.0006.1031.2008/ieee80211'
make: *** [install] Error 2
kinnunen@Atom:~/Desktop/rtl8192u_linux_2.6.0006.1031.2008$
Please help!!!
Re: no rule to make target kernel/bounds.c
Same problem here. Please help!
Re: no rule to make target kernel/bounds.c
same kind of prob here. bump.
Re: no rule to make target kernel/bounds.c
Quote:
Originally Posted by
HubertB
Hi!
Installing the kernel sources using apt / aptitude / synaptic / whatsoever only puts the compressed source code into /usr/src. You need to uncompress the sources:
Code:
$ cd /usr/src
$ sudo tar -xvjf linux-source-$YOUR_VERSION_HERE.tar.bz2
Then just change into the new /usr/src/linux-source-$YOUR_VERSION_HERE directory and built your kernel like you used to :-)
So long
This works, you need to make sure when you compile your code it's pointing to the Linux sources and not the headers. You will see in the error where it's point to. For example:
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-16-generic'
You can see it's still pointing to the headers.