Arch Linux

Werzi2001

Member

Registered: 2012-07-07

Posts: 51

[SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

Hi together,

i cannot start games using wine and optirun anymore. Wine complains about the file /usr/lib/libturbojpeg.so is missing although it is there. Maybe optirun redirects to another
lib instead which is actually missing. Yesterday it worked so i think it has to do with the update of lib32-libjpeg-turbo i installed today.

Thanks for your help.

Yours
Thomas

Edit:
Sorry i made a mistake. The error complains just about "libturbojpeg.so" not "/usr/lib/libturbojpeg.so" so i think "/usr/lib32/libturbojpeg.so" is meant which is actually missing.

Last edited by Werzi2001 (2012-07-08 11:40:58)

aprescott

Member

Registered: 2012-07-07

Posts: 7

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

The .so is removed as part of the (lib32)-libjpeg-turbo package because libjpeg-turbo is not versioned (see: https://bugs.archlinux.org/task/25275 ). There is a bug report at http://sourceforge.net/tracker/?func=de … id=1278161 with an explanation for why there is no versioning, although there is a patch (mentioned in the bug report comments) at http://libjpeg-turbo.svn.sourceforge.ne … vision=820 which includes a dummy version number. As explained in the comments, this is not applied to the stable branch, and probably won't be (based on dcommander's comments).

Since all of the AUR packages dealing with libjpeg-turbo, e.g., libjpeg-turbo-svn, remove this .so for the same versioning reasons, and since the AUR package turbojpeg doesn't install the 32-bit version, possible solutions are:

1. Use abs to make your own patched version of lib32-libjpeg-turbo which doesn't remove these files, and do this every time there's an update to lib32-libjpeg-turbo.
2. Wait for an AUR package which is the lib32 equivalent of turbojpeg, or write your own.
3. See if libjpeg-turbo-svn installs the lib32 version as well as lib if you edit out the rm line from PKGBUILD.

ZekeSulastin

Member

Registered: 2010-09-20

Posts: 266

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

{edit}Beaten to it by the other IRC participant >.>{/edit}

Last edited by ZekeSulastin (2012-07-07 19:33:20)

joi

Member

Registered: 2012-01-07

Posts: 8

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

I can confirm that suggestion 1 works and is quite easy to perform. # $Id: PKGBUILD 73348 2012-07-06 15:36:04Z bluewind $
Here is the PKGBUILD file, I used

Basically all I did was change the version and uncomment the line that deletes the libturbojpeg.so file like so:

#rm "$pkgdir"/usr/lib32/libturbojpeg.{so,a}

Refer to the abs faq if your stuck. https://wiki.archlinux.org/index.php/ABS_FAQ

# Maintainer: Allan McRae <allan@archlinux.org>
# Contributor: Simone Sclavi 'Ito' <darkhado@gmail.com>

_pkgbasename=libjpeg-turbo
pkgname=lib32-$_pkgbasename
pkgver=1.2.0
pkgrel=1
pkgdesc="libjpeg derivative with accelerated baseline JPEG compression and decompression (32-bit)"
arch=('x86_64')
url="http://libjpeg-turbo.virtualgl.org/"
license=('GPL' 'custom')
depends=('lib32-glibc' $_pkgbasename)
makedepends=('nasm' gcc-multilib)
provides=('lib32-libjpeg=8.0.2')
conflicts=('lib32-libjpeg')
replaces=('lib32-libjpeg')
options=('!libtool')
source=(http://sourceforge.net/projects/$_pkgbasename/files/$pkgver/$_pkgbasename-$pkgver.tar.gz)
sha1sums=('4ab00afc9a8d54cd2e7a67aacb9c49e01a8bccac')

build() {
  cd "$srcdir/$_pkgbasename-$pkgver"

  export CC="gcc -m32"
  export CXX="g++ -m32"
  export PKG_CONFIG_PATH="/usr/lib32/pkgconfig"

  sed -i "s|NAFLAGS='-felf64 -DELF -D__x86_64__'|NAFLAGS='-felf32 -DELF -D__x86_64__'|" configure
  ./configure --prefix=/usr --with-jpeg8 --mandir=/usr/share/man --libdir=/usr/lib32 --without-simd
  make
}

package() {
  cd "$srcdir/$_pkgbasename-$pkgver"

  make DESTDIR="$pkgdir/" install

  # do not distributre libturbojpeg as it is unversioned
  #rm "$pkgdir"/usr/lib32/libturbojpeg.{so,a}

  rm -rf "${pkgdir}"/usr/{include,share,bin,sbin}
  mkdir -p "$pkgdir/usr/share/licenses"
  ln -s $_pkgbasename "$pkgdir/usr/share/licenses/$pkgname"
}

Werzi2001

Member

Registered: 2012-07-07

Posts: 51

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

Thanks for all your replies and thanks to joi for the PKGBUILD, works like a charm.

Yours
Thomas

derhamster

Member

Registered: 2012-07-08

Posts: 86

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

I created a lib32-turbojpeg entry in AUR, some hours ago (didn't see this thread until now)
I also provided updated PKGBUILDs for virtualgl, lib32-virtualgl (both were updated to 2.3.1) and turbojpeg (updated to 1.2.1). The pkgrel is set to 0, so DaNiMoTh has the chance to adopt the new versions.

Hopefully everything works with these.

aprescott

Member

Registered: 2012-07-07

Posts: 7

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

Thanks for the packages!

joi

Member

Registered: 2012-01-07

Posts: 8

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

you confuse me, derhamster. I thought lib32-turbojpeg would not be the same package as lib32-libjpeg-turbo similar to turbojpeg not being the same as libjpeg-turbo as described here: http://www.libjpeg-turbo.org/About/TurboJPEG

aprescott

Member

Registered: 2012-07-07

Posts: 7

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

you confuse me, derhamster. I thought lib32-turbojpeg would not be the same package as lib32-libjpeg-turbo similar to turbojpeg not being the same as libjpeg-turbo as described here: http://www.libjpeg-turbo.org/About/TurboJPEG

If you check the PKGBUILD for lib32-turbojpeg, it is the equivalent of turbojpeg but for 32-bit. That is, it only installs the stuff which the official libjpeg-turbo package does not install.

joi

Member

Registered: 2012-01-07

Posts: 8

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

ah, ok. Thanks for that clarification.

aprescott

Member

Registered: 2012-07-07

Posts: 7

Re: [SOLVED] [wine, bumblebee] /usr/lib/libturbojpeg.so missing

ah, ok. Thanks for that clarification.

No problem. The naming isn't great, but I'm not sure there's anything more sensible.