You are not logged in.
Downloaded tarball from:
https://aur.archlinux.org/packages/tint … setlang=en
I get this error when I try to install, google didnt help:
[root@box tint2-0.11]# ls
AUTHORS COPYING INSTALL.txt README.source doc sample
CMakeLists.txt ChangeLog README default_icon.png get_svnrev.sh src
[root@box tint2-0.11]# makepkg
bash: /usr/bin/makepkg: /usr/bin/bash: bad interpreter: No such file or directory
[root@box tint2-0.11]#
Offline
You downloaded the source instead of the package tarball (under Package Actions on the right).
Last edited by Scimmia (2013-03-11 18:55:02)
Offline
https://aur.archlinux.org/packages/ti/t … svn.tar.gz
Is this source?
I have also saved https://aur.archlinux.org/packages/ti/t … n/PKGBUILD into file named PKGBUILD and put that into directory:
[root@box tint2-0.11]# ls
AUTHORS ChangeLog README doc src
CMakeLists.txt INSTALL.txt README.source get_svnrev.sh
COPYING PKGBUILD default_icon.png sample
[root@box tint2-0.11]# makepkg
bash: /usr/bin/makepkg: /usr/bin/bash: bad interpreter: No such file or directory
[root@box tint2-0.11]#
Offline
It looks like you have two separate problems. I didn't look past your first one to see that makepkg can't even find bash.
For the first problem, yes, that link is the package tarball (not the source). Please read https://wiki.archlinux.org/index.php/AUR#Prerequisites to try to understand how to use the AUR.
For the second problem, what is the output of "which bash"?
Edit, third problem, running makepkg as root? Why?
Last edited by Scimmia (2013-03-11 21:34:39)
Offline
Yes I was reading the wiki on AUR before.
Both base-devel and make are installed and I know now that I have to do this as normal user not root but the result is the same:
[box@box tint2-0.11]$ ls
AUTHORS COPYING INSTALL.txt README default_icon.png get_svnrev.sh src
CMakeLists.txt ChangeLog PKGBUILD README.source doc sample
[box@box tint2-0.11]$ makepkg -s
bash: /usr/bin/makepkg: /usr/bin/bash: bad interpreter: No such file or directory
For the second problem, what is the output of "which bash"?
hm sorry I have no idea what you mean.. how can I fix this bash error?
/usr/bin/makepkg exist.. but /usr/bin/bash does not:
[box@box tint2-0.11]$ which bash
/bin/bash
Offline
You are using ArchLinux, not one of it's derivatives, right? /bin/bash should just be a symlink to /usr/bin/bash
If you are on Arch, reinstall the bash package, something is seriously wrong with your installation.
You also keep posting a dir listing that shows all of the source code. It should not be there. Once you get bash working, remove that directory and start again, following the steps in the wiki exactly.
Last edited by Scimmia (2013-03-11 23:07:53)
Offline
Thats right I am using Archlinux.
looks like:
ln -s /bin/bash /usr/bin/bash
fixed the bash error but I have read elsewhere that this is not recommended thing to do..
laters
Offline
Im guessing recent updates have moved bash from /usr/bin/bash to /bin/bash
Some packages may be still looking at the old location, so as stated above run a symlink
root # ln -s /bin/bash /usr/bin/bashTo fix things for now
Arch Linux since 2006
Python Web Developer + Sys Admin (Gentoo/BSD)
Offline
No, updates have done no such thing, bash is still installed to /usr/bin/bash by default in Arch. There is something very wrong with j28's installation if the bash binary is at /bin/bash and the bash package needs to be reinstalled.
Offline
No, updates have done no such thing, bash is still installed to /usr/bin/bash by default in Arch.
I think Crooksey may have gotten it backwards, possibly by accident or misunderstanding--bash has moved into /usr/bin, not the other way around. I've encountered two Arch machines that haven't been updated in quite some time that had exactly this issue, one updated before December of last year and one that hasn't been updated in a long, long time:
# pacman -Qs bash
local/bash 4.2.024-2 (base)
The GNU Bourne Again shell
# pacman -Ql bash
bash /bin/
bash /bin/bash
bash /bin/bashbug
bash /bin/sh
*snip*But in both cases, updating the system and/or bash fixes the issue. The problem then is that makepkg is obviously looking for the bash interpreter at /usr/bin/bash (where it should be, probably a recent change itself) and older versions of the bash package installed it to /bin/bash. This likely occurs when updating pacman separately from the rest of the system and then using makepkg to install something else (and failing or forgetting to update the system completely before continuing on your merry way). I believe this was changed in r175821 from the SVN repo:
r175821 | allan | 2013-01-22 00:47:57 -0700 (Tue, 22 Jan 2013) | 3 lines
upgpkg: bash 4.2.042-2
install to /usr/bin and symlink as needed in /bin - will help with future /bin removalspecifically this PKGBUILD change to bring bash up to the current standard of installing into /usr/bin where everything else is:
./configure --prefix=/usr --with-curses --enable-readline \
- --without-bash-malloc --with-installed-readline \
- --bindir=/bin --mandir=/usr/share/man --infodir=/usr/share/info
+ --without-bash-malloc --with-installed-readline
makeLast edited by Zancarius (2013-03-16 18:39:20)
He who has no .plan has small finger.
~Confucius on UNIX.
Offline