Wine 1.1.17 ..broke?

whaevr · Post by **whaevr** » Fri Mar 13, 2009 10:07 pm

I just compiled wine 1.1.17 from source and then set it up with 32libs like I usually do (ArchLinux 64bit) and then I tried to run winecfg like I always do when I install a new version of wine.

I get this in terminal
"/usr/bin/wine: failed to read ELF header"

Any attempt to run anything except just plain "wine" gives the same message.

I thought at first it was my fault corrupt download or something, but then I did a build using a binary from suse's repos, same result.

austin987 · Post by **austin987** » Fri Mar 13, 2009 10:22 pm

On Fri, Mar 13, 2009 at 10:07 PM, whaevr <[email protected]> wrote:

I just compiled wine 1.1.17 from source and then set it up with 32libs like I usually do (ArchLinux 64bit) and then I tried to run winecfg like I always do when I install a new version of wine.

I get this in terminal
"/usr/bin/wine: failed to read ELF header"

Any attempt to run anything except just plain "wine" gives the same message.

I thought at first it was my fault corrupt download or something, but then I did a build using a binary from suse's repos (http://download.opensuse.org/repositori ... 10.3/i586/), same result.

Works fine here. Can you run a regression test:

http://wiki.winehq.org/RegressionTesting
--
-Austin

vitamin · Post by **vitamin** » Sat Mar 14, 2009 2:32 am

whaevr wrote:I tried to run winecfg like I always do

How exactly?

fullyspenged · Post by **fullyspenged** » Sat Mar 14, 2009 3:56 am

whaevr wrote:I just compiled wine 1.1.17 from source and then set it up with 32libs like I usually do (ArchLinux 64bit) and then I tried to run winecfg like I always do when I install a new version of wine.

I get this in terminal
"/usr/bin/wine: failed to read ELF header"

Any attempt to run anything except just plain "wine" gives the same message.

I thought at first it was my fault corrupt download or something, but then I did a build using a binary from suse's repos, same result.

Hello, I am also using Arch64 and I compiled 1.1.17 the same way I compiled 1.1.11 --> 1.1.16. The reason (I think) why 1.1.17 doesn't work is because the threading binary has changed.

I am not 100% sure, but something drastic has changed and the same PKGBUILDS we used won't work anymore.

whaevr · Post by **whaevr** » Sat Mar 14, 2009 6:06 am

So I'm not the only person experiencing the problem, the maintainer of the bin32-wine-suse confirms he has this problem also.

I'll try and run a regression test and see what happens.

I don't know if this is it, I end up recompiling wine about 6-7 times and it gave me this after it said there were 0 things left to test and I ran "git bisect good" After the bug failed to show up (again)

Code: Select all

[whaevr@myhost wine-git]$ git bisect good
3d35a630c4ae65fb4ab3aaf408a09051d5067b4f is first bad commit
commit 3d35a630c4ae65fb4ab3aaf408a09051d5067b4f
Author: Alexandre Julliard <[email protected]>
Date:   Fri Mar 13 17:07:55 2009 +0100

    Release 1.1.17.

:100644 100644 8385cc10020851af3247913f46062a8e1ea4c232 2f270971bc16f01cbc238d372b66714238294a22 M	ANNOUNCE
:100644 100644 bedcfc48fe833360f51efc9cf88e6a620c2039da 7008ccf9642a4fa39c284393e29b4e660251f931 M	VERSION
:100755 100755 5e3ab39402deeb8aef1c4abacc4f4c2e17f180f6 63fe184217ff228c165cd7975eaf72b85fdde3e3 M	configure

Was testing each build with "./wine winecfg"

I'm a bit confused as to what to do now, I realize I have to reset my bisect and use version 1.1.17 as my "good" but then what?

vitamin · Post by **vitamin** » Sat Mar 14, 2009 12:23 pm

whaevr wrote:I'm a bit confused as to what to do now, I realize I have to reset my bisect and use version 1.1.17 as my "good" but then what?

Just compile wine-1.1.17 from GIT and check if it works on not. I suspect your PKGBUILDS is invalid.

whaevr · Post by **whaevr** » Sat Mar 14, 2009 1:27 pm

Heres the pkgbuild for bin32-wine, see if anyone here can see anything that might cause problems.

Code: Select all

# Contributor: Clement Siuchung Cheung <[email protected]>
# Maintainer: Mikko Seppälä <[email protected]>
# This version needs no modifications to ld.so.conf

_pkgsourcename=wine
pkgname=bin32-wine
pkgver=1.1.17
pkgrel=1
pkgrel32=1
pkgdesc="Interpreter for the Windows 3.x and Win32 APIs"
arch=('x86_64')
url="http://www.winehq.com/"
license=('LGPL')
depends=('lib32-libx11' 'lib32-libjpeg' 'lib32-alsa-lib' 'lib32-libxxf86vm' 'lib32-mesa' 'util-linux-ng' 'lib32-freetype2' 'lib32-fontconfig' 'lib32-libxslt' 'lib32-libxml2' 'lib32-libxcb' 'lib32-libxrender' 'lib32-libxdamage')
provides=('wine')
conflicts=('wine')
install=()
source=("binarynames" "ftp://ftp.heanet.ie/mirrors/ftp.archlinux.org/extra/os/i686/${_pkgsourcename}-${pkgver}-${pkgrel32}-i686.pkg.tar.gz")
md5sums=('b0fd553e2f11fe7553ac1717797befe6' '22b34bd8496dcca00b1b1682079ece25')

build() {
  rm $startdir/src/${_pkgsourcename}-${pkgver}-${pkgrel32}-i686.pkg.tar.gz
  rm $startdir/src/binarynames
  cp -rPfp $startdir/src/* $startdir/pkg/
  install -d $startdir/pkg/opt/lib32/usr/lib/
  mv $startdir/pkg/usr/lib/libwine.so* $startdir/pkg/opt/lib32/usr/lib/
  cd $startdir/pkg/usr/bin/
  
  install -d $startdir/pkg/opt/wine/bin/ $startdir/src/tempscripts/
  for i in `cat $startdir/binarynames` ; do
  mv $i $startdir/pkg/opt/wine/bin/
  echo -e '#!/bin/sh\n#wrapper for replacename\nPATH="/opt/wine/bin/:$PATH"\nLD_LIBRARY_PATH="/opt/lib32/usr/lib/:/opt/lib32/lib/:$LD_LIBRARY_PATH" linux32 /opt/wine/bin/replacename "$@"' > $startdir/src/tempscripts/$i
  sed -re "s/replacename/$i/" -i $startdir/src/tempscripts/$i
  install -m755 $startdir/src/tempscripts/$i $i
  done

  # PPD fix
  mkdir -p $startdir/pkg/opt/lib32/usr/share/
  ln -s /usr/share/wine $startdir/pkg//opt/lib32/usr/share/wine
  
  # These should NOT be needed!
  # Fakeroot causes trouble for some users again?
  cd $startdir/pkg/usr/lib/
  chmod 755 wine
  cd wine
  chmod 755 *so
  chmod 644 *.def *16 *.a
  # Added /usr/share/wine workaround for some users
  cd $startdir/pkg/usr/share/
  chmod 755 wine
  cd wine
  chmod -R 644 *
  chmod 755 fonts
}

vitamin · Post by **vitamin** » Sun Mar 15, 2009 1:21 pm

whaevr wrote:Heres the pkgbuild for bin32-wine, see if anyone here can see anything that might cause problems.

Take that with your distro. If vanilla Wine version works it's not Wine's problem.

whaevr · Post by **whaevr** » Sun Mar 15, 2009 1:26 pm

It is the pkgbuild, other users confirm that they can get the i686 version working fine that they compiled. Although other x86_64 users are also having the same issue as me.

Alright here's the wrapper file used to run the 32bit wine executable.

Code: Select all

#!/bin/sh
#wrapper for wine
PATH="/opt/wine/bin/:$PATH"
LD_LIBRARY_PATH="/opt/lib32/usr/lib/:/opt/lib32/lib/:$LD_LIBRARY_PATH" linux32 /opt/wine/bin/wine "$@"

There was a change to the wine executable this release that's causing this error, with this wrapper, previous versions of the executable are 5.8kb 1.1.17 is 8.8kb

Devs any help? =/

Wine 1.1.17 ..broke?

Wine 1.1.17 ..broke?

Wine 1.1.17 ..broke?

Re: Wine 1.1.17 ..broke?

Re: Wine 1.1.17 ..broke?