You are not logged in.
This is the error I get trying to build yaourt or yaourt-git.
==> Making package: yaourt 1.0.1-1 (Sun Apr 1 11:34:45 EDT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found yaourt-1.0.1.tar.gz
==> Validating source files with md5sums...
yaourt-1.0.1.tar.gz ... Passed
==> Extracting Sources...
-> Extracting yaourt-1.0.1.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
make: Nothing to be done for `all'.
==> Starting package()...
/bin/install -d /home/conner/yaourt/pkg/usr/bin
/bin/bash: /bin/install: No such file or directory
make: *** [install] Error 127
==> ERROR: A failure occurred in package().
Aborting...
Offline
Check your $PATH, 'install' lives in /usr/bin/install.
Edit: Nope, that's not it, I get the same error.
You can edit the PKGBUILD and change 'install' to '/usr/bin/install'.
Last edited by karol (2012-04-01 20:22:19)
Offline
Thanks karol.
Offline
Hello!
Same problem here.
Doing what karol suggested solved the Error 127 problem, but it still doesn't work: I get an empty (0,00 mb) package that only "seems" to install yaourt: pacman recognize it as installed but if I type "yaourt" I get the command not found.
Offline
I also had this problem. I put a line in the PKGBUILD right before the install line to 'sed' the /bin/install in the Makefile to /usr/bin/install and it worked perfectly.
...
package() {
cd $srcdir/$pkgname-$pkgver/
sed -i 's|/bin/install|/usr/bin/install|' Makefile
make PREFIX-/usr sysconfdir=/etc localstatedir=/var DESTDIR=$pkgdir install
}
...
EDIT: fixed one typo - there may be others as the sed line was not copied from a working version of the PKGBUILD, but rater reconstructed from memory.
EDIT AGAIN: I guess this is similar to Karol's point. However, it seems the problem is in the Makefile not the PKGBUILD itself.
Last edited by Trilby (2012-04-04 14:16:33)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
EDIT AGAIN: I guess this is similar to Karol's point. However, it seems the problem is in the Makefile not the PKGBUILD itself.
I think you're right as it seemed really weird that the PKGBUILD would break all of a sudden, but I was too lazy to dive deeper into this ;P
Offline