You are not logged in.
I don't know if its possible but when I installed the latest wine release (1.1.17) and try to run anything I get the following
"/usr/bin/wine: failed to read ELF header"
Happens on anything I try and run with wine except just "wine"
I made this package the same way I usually do. First I downloaded the 1.1.17 source code from sourceforge, then I dropped it in the same directory as the wine i686 pkgbuild. Then I schroot to arch32, and run makepkg. After thats built I drop that package in the same directory as the bin32-wine pkgbuild, and then run makepkg -i
When that didn't work I tried using the bin32-wine-suse package, thinking that somehow my compile was messed up, or my download was corrupted.
Same thing. So I was wondering if an i686 user can confirm that 1.1.17 works on arch, and then is it possible that the bin32-wine pkgbuild is somehow doing this?
So for now, I'm using wine 1.1.16 which I compiled and installed using the first method.
My edge..it isn't bleeding!
Offline
I can confirm my own wine-1.1.17-i686 works on i686, but when used with bin32-wine throws up the "/usr/bin/wine: failed to read ELF header" junk.
Offline
Just to clarify (and double-post.. sorry!) the same i686 package also works fine in a 32-bit chroot environment on a 64-bit Arch, so either there's an issue with one of the lib32 packages, or the way bin32-wine is wrapping the wine binaries/libs.
Sorry I can't be more help.
Offline
I think its the way the package is wrapping the wine binaries, could someone please take a look at this? Here's the wrapper it uses.
#!/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 "$@"
Offline
I've been having the exact same problem with bin32-wine-suse on x86_64, and for the life of me I can't solve it. This is particularly bad since I volunteered to maintain the package and can't update it until this is fixed.
What would cause a "failed to read ELF header" error in the first place? Google is of no help in this issue.
Offline