You are not logged in.
patching file vloopback.c
patching file vloopback.c
Hunk #2 succeeded at 172 (offset -1 lines).
Hunk #3 succeeded at 185 (offset -1 lines).
make -C /lib/modules/2.6.32-ARCH/build SUBDIRS=/tmp/yaourt-tmp-ets/aur-vloopback/vloopback/src/vloopback-1.2 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.32-ARCH/build'
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build vloopback package.
I have had this same error with avld
patching file video_device.c
patching file video_device.c
make -C /lib/modules/2.6.32-ARCH/build M=/tmp/yaourt-tmp-ets/aur-avld/avld/src/avld_0.1.4 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.32-ARCH/build'
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build avld package.
I read on linuxquestions that it has to do with the make files.
it's clear that you are missing a rule in your Makefile in the `/home/mac/projects/drivers' directory, I think you should have a look in your Makefiles
from http://www.linuxquestions.org/questions … p.-145676/
Others don't seem to have this complaint on the AUR, so I thought it could just be my version/setup of Arch linux.
Facts:
I'm using yaourt to use this
If I use makepkg myself same error occurs
Happens only with packages related to modules
I'm using
Kernel : Linux 2.6.32-ARCH (i686)
Compiled : #1 SMP PREEMPT Fri Jan 29 08:50:05 UTC 2010
C Library : GNU C Library version 2.11.1 (stable)
Default C Compiler : GNU C Compiler version 4.4.3 (GCC)
Last edited by 3]) (2010-02-28 04:56:57)
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
i have the same problem, do you resolve it ?
Offline
This
make -C /lib/modules/2.6.32-ARCH/build M=/tmp/yaourt-tmp-ets/aur-avld/avld/src/avld_0.1.4 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
looks odd. Should you really be entering an actual system directory when building a package?
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
The package is missing a build dependency on kernel headers. Check that installing them solves the problem for you. If it does, please mark the thread as solved and leave a message on AUR.
Last edited by grey (2010-02-17 21:47:26)
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
The package is missing a build dependency on kernel headers. Check that installing them solves the problem for you. If it does, please mark the thread as solved and leave a message on AUR.
I have installed
kernel26-headers-2.6.32.8-1
kernel26-lts-headers-2.6.27.45-1
linux-api-headers-2.6.32.5-2
Yet I get this output
==> Continue the building of avld ? [Y/n]
==> ----------------------------------------------
==>Y
==> Install or build missing dependencies for avld:
==> Building and installing package
==> Making package: avld 0.1.4-2 i686 (Thu Feb 18 19:52:25 ICT 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found avld_0.1.4.tar.bz2 in build dir
-> Found avld_0.1.4.patch in build dir
-> Found bad.patch in build dir
==> Validating source files with md5sums...
avld_0.1.4.tar.bz2 ... Passed
avld_0.1.4.patch ... Passed
bad.patch ... Passed
==> Extracting Sources...
-> Extracting avld_0.1.4.tar.bz2 with bsdtar
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
patching file video_device.c
patching file video_device.c
make -C /lib/modules/2.6.32-ARCH/build M=/tmp/yaourt-tmp-ets/aur-avld/avld/src/avld_0.1.4 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.32-ARCH/build'
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build avld package.
Still unable to install the program.
For people interested in compiling this program: http://aur.archlinux.org/packages.php?ID=33916
Last edited by 3]) (2010-02-18 12:57:19)
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
First, don't use yaourt when you try to debug a build failure - use makepkg directly. That eliminates one source of possible error.
Second: I cannot reproduce the problem. Things start to diverge here:
You:
make -C /lib/modules/2.6.32-ARCH/build M=.../avld_0.1.4 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
Me:
make -C /lib/modules/2.6.32-ARCH/build M=.../avld_0.1.4 modules
make[1]: Entering directory `/usr/src/linux-2.6.32-ARCH'
Try to execute the build() function step by step. The crucial step is the make command in the avld source directory. You can actually call it directly: go there and do 'make all'. Let me know what you get.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
[me@memobile avld_0.1.4]$ make all
make -C /lib/modules/2.6.32-ARCH/build M=/home/me/Me_Stuff/Downloads_ALL/ArchBuilds/avld/src/avld_0.1.4 modules
make[1]: Entering directory `/lib/modules/2.6.32-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.32-ARCH/build'
make: *** [all] Error 2
Thats the output I get when building using the source directory with "make all".
In the Makepkg I have noticed,
mkdir -p ${pkgdir}/lib/modules/`uname -r`/kernel/drivers/misc
cp avld.ko ${pkgdir}/lib/modules/`uname -r`/kernel/drivers/misc
Something must be wrong with the ${pkgdir} variable on my computer then as it is building the whole module in the wrong location(lib/modules/ instead of /usr/src).
I guess if I change that symlink(if it is one) or variable pkgdir I could build it successfully. I will try.
Update: changing the ${pkgdir} to /usr/src/ didn't do a thing, even if it might have sounded absurd to try, I tried and failed.
Last edited by 3]) (2010-02-19 06:51:24)
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
Did you by any chance create a directory /lib/modules/2.6.32-ARCH/build at some point? I just realized that on my system
ls -l /lib/modules/2.6.32-ARCH/build
lrwxrwxrwx 1 root root 34 Feb 9 14:14 /lib/modules/2.6.32-ARCH/build -> ../../../usr/src/linux-2.6.32-ARCH
The symlink also explains why 'make -C /some/where ...' leads to a screen message 'entering directory /else/where'.
${pkgdir} is fine. You really are meant to build in /lib/modules/2.6.32-ARCH/build, or at least using the Makefile that is there.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
after doing
sudo pacman -Syu
I can install the aur package vloopback-svn with no error
Offline
Did you by any chance create a directory /lib/modules/2.6.32-ARCH/build at some point? I just realized that on my system
ls -l /lib/modules/2.6.32-ARCH/build
lrwxrwxrwx 1 root root 34 Feb 9 14:14 /lib/modules/2.6.32-ARCH/build -> ../../../usr/src/linux-2.6.32-ARCHThe symlink also explains why 'make -C /some/where ...' leads to a screen message 'entering directory /else/where'.
${pkgdir} is fine. You really are meant to build in /lib/modules/2.6.32-ARCH/build, or at least using the Makefile that is there.
My build directory is...
me@memobile build]$ ls -l /lib/modules/2.6.32-ARCH/build
total 0
Yes, I did create a build directory at some point I believe(as another app. also needed it).
So it seems that I must make the build directory a symlink by itself to the /usr/src/linux-2.6.32-ARCH.
Will try it and see if that works.
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
my output for:ls -l /lib/modules/2.6.32-ARCH/build
lrwxrwxrwx 1 root root 27 Feb 21 12:24 linux-2.6.32-ARCH -> /usr/src/linux-2.6.32-ARCH/
Still doesn't seem to match up yours,would be nice if you could provide the /../../..,
as I'm still getting the same errors even when they are entering the/usr/src/linux-2.6.32-ARCH/ directory.
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
after doing
sudo pacman -Syu
I can install the aur package vloopback-svn with no error
I have done that with powerpill (as the qt dependency error doesn't allow it to fully update everything if 1 package can't update).
Hasn't changed a thing for me.
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
after doing
sudo pacman -Syu
I can install the aur package vloopback-svn with no error
I have done that, no change whatsoever.
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline
I solved the issue!
All I had to do was to remove the build directory in /lib/modules/2.6.32-ARCH/
and then install the kernel26-header file which creates its own build directory(which works flawlessly).
After that the result was ...
==> Continue installing avld? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>Y
Would like to thank the following people who helped me.
grey-who pointed out the flaw in the build directory, and hinted at something being wrong with kernel headers(which I couldn't install before due to a conflict with the build folder in /lib/modules/2.6.32-ARCH/.
nullren-who told me the exact name of the kernel headers
and the rest of you who checked this thread.
Last edited by 3]) (2010-02-28 04:56:37)
“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare
Offline