You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2009-11-12 23:19:48
- murfMan
- Member
- Registered: 2009-10-27
- Posts: 161
build failed
hi im trying to build the package, mpdscribble, from the AUR
and i get this:
==> Starting make...
make: *** No rule to make target `install'. Stop.
==> ERROR: Build Failed.
Aborting...what do i do?
Offline
#2 2009-11-12 23:56:12
- tdy
- Member
- From: Sacremende
- Registered: 2008-12-14
- Posts: 440
Re: build failed
That error doesn't make sense since the first command is ./configure. Did you modify the PKGBUILD? Are you using the newest mpdscribble PKGBUILD? Describe the entire process you used to build the package.
Offline
#3 2009-11-13 02:07:34
- murfMan
- Member
- Registered: 2009-10-27
- Posts: 161
Re: build failed
i downloaded the tarball from the AUR and i used makepkg
there is no configure file 
[murf@arch mpdscribble-git]$ ls
PKGBUILD mpdscribble.conf.example mpdscribble.init mpdscribble.install
[murf@arch mpdscribble-git]$ ./configure
-bash: ./configure: No such file or directory
Last edited by murfMan (2009-11-13 02:08:05)
Offline
#4 2009-11-13 02:41:06
- Ranguvar
- Member
- Registered: 2008-08-12
- Posts: 2,549
Re: build failed
What he's saying is that in the PKGBUILD, it does a configure step first, whereas your output shows make running first.
The configure file isn't there for obvious reasons -- that's just an AUR tarball containing Arch-specific stuff. makepkg downloads the real source and compiles that.
Offline
#5 2009-11-13 02:51:52
- tdy
- Member
- From: Sacremende
- Registered: 2008-12-14
- Posts: 440
Re: build failed
i downloaded the tarball from the AUR and i used makepkg
there is no configure file
[murf@arch mpdscribble-git]$ ls
PKGBUILD mpdscribble.conf.example mpdscribble.init mpdscribble.install
[murf@arch mpdscribble-git]$ ./configure
-bash: ./configure: No such file or directory
Well, this sheds a little more light on your situation. You were trying to build the mpdscribble-git package, not mpdscribble.. but in any case both packages work fine here.
You also left out almost the entire build output in your original post. Paste the entire output from makepkg here, including the configure output. Those 4 lines you showed from your first post do not help at all.
Last edited by tdy (2009-11-13 03:43:34)
Offline
#6 2009-11-13 17:11:01
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: build failed
Perhaps a description of the proper use of the aur download is in order.
The "tarball" is firstly downloaded and "untarred". This results in a "PKGBUILD" file which may include other items as well. These must be placed in a directory such as "/var/local" (should be an empty directory).
Then the PKGBUILD can be opened as needed for possible editing. Not always needed, however.
User then must change directory (CD) to /var/local and begin "makepkg". It is possible to "run-as-root" with a switch "--asroot" but is not recommended since the users system may be compromised should the package contents impact other packages and their dependencies.
This info is probably available in a wiki but this synopsis may be helpful for understanding by new users.
Good luck..........
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#7 2009-11-19 15:12:36
- Runiq
- Member
- From: Germany
- Registered: 2008-10-29
- Posts: 1,053
Re: build failed
Try adding autoconf and automake to makedepends. I think I've seen this with several mp*-git packages over the last few weeks.
Offline
Pages: 1