On 08.05.14 22:17, Robert Brown wrote:
On 08/05/14 21:48, Erik Christiansen wrote:
On 08.05.14 20:49, Robert Brown wrote:
make: Entering directory `/home/user/linux-sunxi' scripts/Makefile.build:44: /home/user/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0-master/Makefile: No such file or directory make[1]: *** No rule to make target `/home/user/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0-master/Makefile'. Could you please show us:
$ ls -l \ e This is what is puzzling me. The folder is
/home/user/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0-master
and not /home/user/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0-master/Makefile The Makefile is in this folder and I expected that the make command would find and run this Makefile.
If you had done a "cd" into the directory, then yes, a simple "make" should work like a "./make". Were you in the directory?
The output of ls -la is attached.
Actually, all I was after was:
-rw-r--r-- 1 root root 1675 Jan 17 16:53 Makefile
The ls needed to be run as an ordinary user, if that is how "make" was run. It is all moot if you're running "make" as root.
I note that there is a sub-folder folder inside this one with another Makefile and the *2832* source files. So maybe I need to cd to that folder and run the command there.
No. Running "make" in the top directory will recurse through the subdirectories, under direction from the "Makefile" in that directory, so long as you are in that directory when running "make". Erik -- You can't have everything. Where would you put it? - Steven Wright