I have down loaded: slapt-get-0.10.2h-i386-1.tgz I have read the install directions:
Quote:
- Using pkgtools: ----------------
To install:
$ make pkg
$ installpkg ./pkg/slapt-get-${VERSION}-${ARCH}-${RELEASE}.tgz
When I try make pkg, I get:
Code:
root@darkstar:/home/rob# make pkg
make: *** No rule to make target `pkg'. Stop.
I guess that I do not understand the instructions?
I am getting an error as below.
How do I resolve the error: make[2]: *** No rule to make target `', needed by `mpg123'.
How can I resolve this error.
I want to gave much details as possible. working directory (~/a1/shell) in the shell directory i have Makefile. also in the shell directory i have subdirectory's (obj, src, include)
My current Makefile
Quote:
#What needs to be built to make all files and dependencies
clean:
# End of Makefile
I wanted it so: all .o files are created in the obj subdirectory, and my application, sshell, is created in the shell directory.
I am getting this error when i run the make run: No rule to make target 'shell.h', needed by 'shutil.o'. stop
I am following the instructions on Section 8.1.* Device Driver ConceptsHere I was able to proceed till section 8.1.4.After making the hello.c file,the make file and patching the Kconfig as mentioned,I tried to run the $ make ARCH=ARM CROSS_COMPILE=xscale_be- gconfig This gave error as:make: *** No rule to make target `gconfig'. Stop.I am not sure if my kernel is correctly compliled,but I was able to complie and build the kernel for arm before by cloning the kernel and building from the following link without any error. https://omapzoom.org/gf/project/omap...ux+OMAP+Kernel
View 2 Replies View RelatedAfter reading all the forum entries and tutorials I could find, which all make it sound very easy to do, however I type the command 'make' in the folder where I have the "rtl8192su_linux_2.4_2.6.0003.1019.2009.tar.gz " unzipped and get the following output:
make[1]: Entering directory `/lib/modules/2.6.35.6-45.fc14.i686/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.35.6-45.fc14.i686/build'
[code]....
I am getting this following error when I do compilation..Please let me know what is missing
ubuntu@ubuntu-desktop:/home/swamy/ttviewer/uvcvideo-2.6.32$ make
make -C /lib/modules/2.6.31-203-gee1fdae/build SUBDIRS=/home/swamy/ttviewer/uvcvideo-2.6.32 modules
make[1]: Entering directory `/usr/src/linux'
[code]....
My make file has the following lines:
blah blah
INCLUDES= -I./src
-I./include
-I$(PROJECTPATH)/myproject/libs/liburi/include
LDFLAGS+= -L$(PROJECTPATH)/myproject/libs/liburl/
[code]....
The LDFLAGS specifies the library path, which is specified as -L$(PROJECTPATH)/myproject/libs/liburl/ When I check this directory on my machine I see that the file: liburi.so.1 is indeed there.
i'm trying to install driver for some PCI device but i have problems with it - when i run it it gives me an error
Code: Select allmake: Entering directory `/lib/modules/2.6.32-5-686/build'
make: *** No rule to make target `modules'. Stop.
make: Leaving directory `/lib/modules/2.6.32-5-686/build'
i've tried to find solution in internets but have no success usually they say that problem is that ppl forget to download kernel-headers and kernel-sources or unpack kernel-sources or make symlink usr/src/linux but i've done it all and the result is the same.i think the root of problem is that `/lib/modules/ 2.6.32-5-686/build' folder is empty but there have to be this RULE, so what i have to do to have it there? my system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686.
make /usr/bin/make all-am
make: Nothing to be done for `/usr/bin/make'.
make: *** No rule to make target `all-am'. Stop.
whats wrong with this???
I'm using build root to make an embedded rootfs and compile some code. However I get the following error
make: *** No rule to make target `linux26', needed by `linux-fusion'. Stop.
I am using Fedora 8. I tried to install ns 2.31. But error came as " No rule to make target "VERSION" needed by gen/version.c".
View 2 Replies View RelatedI've had qmail running on a server for three years, almost forgot how difficult that installation was. I got away with it because I downloaded Qmail Rocks and followed all their instructions step by step. However, Qmail Rocks is based on qmail 1.03. I just had to install qmail on a new server, so this time I looked around and found netqmail 1.06 and decided to go with it, following the instructions on Life With Qmail. It was a good decision. A read a lot more documentation and now I understand qmail a lot better.
But I can't get past one point: authentication. Consider this test on Qmail Rocks:
Code:
telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 somewhere.anywhere.com ESMTP
ehlo localhost
250-somewhere.anywhere.com
250-AUTH LOGIN CRAM-MD5 PLAIN
250-AUTH=LOGIN CRAM-MD5 PLAIN
250-STARTTLS
250-PIPELINING
250 8BITMIME
starttls
220 ready for tls
quit
quit
Connection closed by foreign host.
That test works fine on my old server. But qmail behaves differently on my new server:
Code:
# netqmail-1.06> telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 domain.com ESMTP
ehlo localhost
250-domain.com
250-PIPELINING
250 8BITMIME
starttls
502 unimplemented (#5.5.1)
quit
221 domain.com
Connection closed by foreign host.
That same page on Qmail Rocks says that I need to have a certificate, the procedure is described here. The installation procedure given by LWQ does not include that step. Running 'make cert' inside the source directory of netqmail-1.06 does not work:
Code:
# netqmail-1.06> make cert
make: *** No rule to make target `cert'. Stop.
In my vast ignorance, I copied /var/qmail/control/servercert.pem from my old server over to the new one. I also fixed all ownership and permissions. I don't know if I am allowed to do that. But although those are two different boxes, I am in fact installing the same domain in the new box. The new server is going to replace the old one as soon as it's running perfectly. I restarted qmail and... authentication still does not work.
Code:
anisha@linux-p0mg:~> uname -r && cat /etc/*release
2.6.25.5-1.1-pae
openSUSE 11.0 (i586)
VERSION = 11.0
My small Makefile:
Code:
obj-m += serialPortISR.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
Errors I receive:
Code:
anisha@linux-p0mg:~/Desktop/serialPortISR_31_10_09> make
make -C /lib/modules/2.6.25.5-1.1-pae/build M=/home/anisha/Desktop/serialPortISR_31_10_09 modules
make[1]: Entering directory '/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory '/usr/src/linux-2.6.25.5-1.1-obj/i386/pae'
make: *** [all] Error 2
I am compiling libmp3lame from svn and I got following error No rule to make target `basic.html', needed by `all-am'. Stop. which package am I missing.....??
View 9 Replies View RelatedI am trying to compile a kernel in the following directory:/usr/src/kernels/2.6.30.9-102.fc11.x86_64
Note I am not trying to build an rpm but just do a simple make. After configuring with make menuconfig I issue the make command and get the following error:
Code:
[root@compaq 2.6.30.9-102.fc11.x86_64]# make
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
make[1]: *** No rule to make target `missing-syscalls'. Stop.
make: *** [prepare0] Error 2
how to resolve this error? It seems to be fedora-centric.
I am relatively new to linux and am running into a problem. I just got a new laptop and need to configure/install it's wireless driver but am getting an error when running "make". The error is: make[1]: Entering directory `/lib/modules/2.6.37.1-1.2-desktop/build' make[1]: *** No rule to make target `modules'. Stop.
I have scoured these forums and know that others have the same issue (when configuring other drivers/programs). I am sorry if this post is redundant. It sounds like the Makefile is pointing to the wrong directory. I am using opensuse 11.4, have make and gcc installed. My kernel is linux-2.6.37.1-1.2 (I just re-installed the desktop kernel to make sure it was up to date). The driver I am trying to install is located here: AUR (en) - rtl8192ce.
Another forum suggests pointing somewhere in the /usr/src/linux-2.6.37.1-1.2 directory instead. Is this correct? Should I be pointing to a folder within this? I am not a programmer but any description about what I am actually putting in this directory and why would be awesome (so I can learn a bit more). Or just helping me solve the problem would be great too.
I am trying to install ns2.1b5 on fedora and I am getting the following error:
No rule to make target `VERSION', needed by `gen/version.c'
I'm attempting to build cloog-ppl-0.15.10 but even the configure script tells that everything look good, "make" complains saying "No rule to make target `m4/libtool.m4`, ...". I'm running Scientific Linux 5.5 on a x86_64 machine.
View 1 Replies View RelatedI have googlled and get these commands to install extracted .tar.gz file such as ./configure, make and make install, after extraction it becomes a directory called eclipse. But when i giving these commands also i got error like this
[Code].....
I want to install EVMS n machines with openSuse 11.2. The EVMS installation procedure (EVMS: Installation: Installing the EVMS Tools), point 3, says to do: "make install".
I'm in the correct folder, there is the file Makeinstall.ini, but just try to run the command I've an error (make cannot have install like target).
this is my output:
linux-vxth:/usr/src/evms-2.5.5 # ls
.makefile.swo INSTALL.initrd aclocal.m4 engine po
.makefile.swp Makefile.in autoconf include tests
COPYING PLUGIN.IDS config.h.in intl ui
[code]...
I tried too rename "Makefile.in" into "makefile" and "make.rules.in" into "make.rules", but then I have other problems
I have an old version of DSL installed, followed by XP. On a further partition I installed Debian 6. Installation of Debian went smoothly, including the final detection of the other two OS for Grub. I had expected that the Debian-version of Grub would override/overwrite the one that came when I installed DSL.
It did not - when I boot, Grub comes up with the old DSL menu, in which Debian is not included.
From what I've been reading about Grub, there's two "fases", first in MBR, that points to the second part where the actual boot-commands are given, in my case stored in DSL.
When I open the Grub config-file in Debian, both DSL and XP are correctly listed.
Now I'm not sure what to do - I'm a bit hesitant to try and point grub-fase-1 to Debian (if I can write the correct lines at all, I'm very insecure on that) - if that fails, I cannot boot at all. But I'm not really sure either how to formulate a new rule in the DSL-grub, to make Debian boot from the existing menu.
I am trying to install iscsi-target on centos 5.4 i386. When I go into the iscsi-target directory and type make I get the following error:
[root@cluster-storage iscsitarget-1.4.19]# make
cc: /lib/modules/2.6.18-164.el5/build/include/linux/version.h: Datei oder Verzeichnis nicht gefunden
cc: keine Eingabedateien
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -lt: unary operator expected
make -C usr
make[1]: Entering directory `/opt/iscsitarget-1.4.19/usr' .....
make: *** [kernel] Fehler 2
I recently bought a pci multi io card to give my pc 2 parallel ports. For Linux, Moschip supply the source plus makefile and instructions. I ran make as root and got an error message
make: *** /lib/modules/2.6.31.12-0.2-desktop/build/: No such file or directory. So I created a folder called build in /lib/modules/2.6.31.12-0.2-desktop but that isn't good enough as I still get an error cannot make target modules. So I assume there must be something in the build folder. So what packages do I have to install to get the correct environment to be able to build the driver? Has anyone done this and can supply the driver for 11.2?
I am trying to create apache rule which will redirect each request not ending with .php prefix to php prefix. I am trying to make such a rule for hours, but none of my works.
Example: I don't know syntax of rewrite rules, but I'd like to make something like this:
RewriteRule ^(.*)(NOT .php) $1.php
(so everything not ending with .php will end in everything with .php extension.
EDIT: Maybe better question would be "how to negate string group" or "is not equal to string"...
To an empty disk I installed:
1) Windows XP & then shrank it's partition to make room for OpenSuse) 2) OpenSuse with grub installed on the MBR (& then shrank the home partition & created a new root and home partition for Slackware 13.1). These two OSes dual-booted properly 3) Slackware 13.1 with LiLo installed to the superblock of the Slackware root partition (sda8). How do I get Slackware to be a 'working' selection on the boot menu?
You might be asking why would I want to this? I will tell you why. My wife. She has grown up using Windows. The jump from Windows XP to 7 wasn't as bad as I thought it would be for her. I just had to show her where things changed to for about 10-20 minutes and that was that.
I did a trial run with Ubuntu for about a month using Gnome and not her cup of tea. So now I did a search on the Internet and came up with a Gnome solution here is the link:
http://aminesoft.wordpress.com/2009/...ike-windows-7/
And a KDE link:
http://www.kde-look.org/content/show...content=104232
But both websites are oriented towards Ubuntu/Kubuntu. I am just wondering if this will work with Slackware???
My wife likes a speedy system almost as much as I do. She also like the Search field when you click on the Start menu in Windows 7, the taskbar at the bottom, the big red X in right hand corner of the windows.
I just hope I can go this route and change it to look like Windows 7. I will be very happy and so will my wife of course.
I have done several attempts to build a local mirror of Salckware 13.0. There are two problems: I have to wait very long for a connection, they appear error during a connection which broke it so I have to restart. Is there any other way to build mirror? I am using Alien Bob scripts. Never before happened something like that. The connections with common web pages (google, etc) work well. Maybe I should look for some other mirror than those listed in mirror-slackware-current.sh.
[code]....
I notice that when you try to Make link to any file or folder form context menu, It just copy the same file size? even when i tried to copy the link to external storage disk..
View 1 Replies View RelatedI need to modify fs/open.c and fs/read_write.c to make my modifications. I cannot find any options in 'make menuconfig' to make these files modules rather than compiled elements. I'm thinking these cannot be modules because the file system won't work without open.c and read_write.c. Is this correct - I cannot compile fs/open.c and fs/read_write.c as modules, only as compiled elements? Or, is there some way for a module to overwrite these routines when the module is installed and re-enable the routines when the module is removed?
View 3 Replies View RelatedI build and use a custom kernel, and use the nvidia driver. This is on debian stretch.
By default, I build the image and headers packages with this line:
CONCURRENCY_LEVEL=8 nice -n19 ionice -c3 fakeroot make-kpkg --initrd --append-to-version=-something --revision=1 kernel_image kernel_headers
These kernel sources are usually the sources from debian, with a couple of more patches that I add. It appears that for nvidia-driver package versions higher than 352.79-1, the kernel headers/sources need to be prepared with 'make prepare' and 'make prepare scripts'. It's that simple. I concluded this after the nvidia dkms build failed on my custom kernel, but then succeeded after I pointed it to the full sources, but only after running 'make prepare' and 'make prepare scripts' on them. The problem is that this make-kpkg scheme doesn't appear to do this, or if it does, it doesn't properly include in the headers everything that it should.