[Solved] Toxic won't open and makepkg fails to reinstall it

Question

Hi there, this is my first time posting in these forums and I hope I'm in the right place.
I use the CLI tox client Toxic as a method for secure communication with friends etc. and I haven't encountered a problem with it before today. I'm not sure what happened but when I tried to run in it my terminal I received this error:
toxic: error while loading shared libraries: libsodium.so.10: cannot open shared object file: No such file or directory
I figured it was a problem with libsodium so I decided to reinstall it, but I still had the same problem. I replaced libsodium with libsodium-git and still the error persists.
The next course of action I tried was to reinstall Toxic from the AUR. I use the git package so I typed:
yaourt -S toxic-git
The package didn't install however and I received this error when the machine tried to build the package:
Makefile:56: recipe for target 'global_commands.o' failed
make: *** [global_commands.o] Error 1
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build toxic-git.
==> Restart building toxic-git ? [y/N]
==> ----------------------------------
Restarting the build returns the same error, and the regular toxic package also will not build.
I've been using Arch for a few months now, but I've never encountered a problem like this before. Does anyone know what I can do to get Toxic working again? Any help would be greatly appreciated, thanks!
Last edited by handles (2014-08-28 21:07:49)

Answer 1

Lone_Wolf wrote:libsodium was upgraded to version 0.7 on 2014-08-27 , and there appears to have been a so-name bump to libsodium.so.13 .
I did a quick check on my system and it would seem that the required libsodium.so.10 is missing, but libsodium.so.13 is present.
pkgfile -l libsodium
community/libsodium /usr/lib/
community/libsodium /usr/lib/libsodium.so
community/libsodium /usr/lib/libsodium.so.13
community/libsodium /usr/lib/libsodium.so.13.0.0
Thanks for letting me about the version change.
Lone_Wolf wrote:You'll have to rebuild everything from aur that uses libsodium against the new version.
I've never had to rebuild a package against a new version of a library before, so I'm going to use this as a good learning opportunity. I spent a good hour and a half searching various Arch wiki pages and forums, but I don't know how to do this. Do I need to edit something in the PKGBUILD file when I go to download the package from the AUR?
The PKGBUILD file looks for toxic-git looks like this:
# Maintainer: Florian Hahn <[email protected]>
pkgname=toxic-git
pkgdesc='CLI client for tox, a Skype replacement that respects your privacy'
license=('GPL3')
pkgver=0.r1134.efe61e3
pkgrel=1
depends=('tox-git' 'ncurses' 'libconfig')
makedepends=('git')
conflicts=('toxic')
provides=('toxic')
arch=('i686' 'x86_64')
url=('http://tox.im')
source=('git+https://github.com/Tox/toxic.git')
md5sums=('SKIP')
optdepends=(
'openal: audio notifications'
'freealut: audio notifications'
_gitname=toxic
pkgver() {
cd "${srcdir}/${_gitname}"
printf "0.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
build() {
cd "${srcdir}/${_gitname}/build"
make PREFIX=/usr
package() {
cd "${srcdir}/${_gitname}/build"
make PREFIX=/usr DESTDIR="${pkgdir}" install
PKGBUILD (END)
I don't see any references to libsodium within this file though, so I'm not really certain what I should be doing to get to compile against the new libsodium v0.7.0 .
If anyone could point me in the right direction, I would really greatly appreciate it.
Last edited by handles (2014-08-28 20:57:56)