wine: ld-elf.so.1 not found

Andresen, Jason jandrese at mitre.org
Wed Jul 26 18:47:08 UTC 2006


I'm having a very strange problem with Wine.  It apparently refuses to
see ld when starting:

<escaflowne/p7> (72 ~): wine
ELF interpreter /libexec/ld-elf.so.1 not found

Even though it's obviously on the system:
<escaflowne/p7> (74 ~): ls /libexec
ld-elf.so.1     ld-elf.so.1.old

Ktrace doesn't really provide much of anything helpful since even ld
won't start:

<escaflowne/p7> (77 ~): ktrace wine
ELF interpreter /libexec/ld-elf.so.1 not found
[1]    90037 abort      ktrace wine
<escaflowne/p7> 134 (78 ~): kdump
 90037 ktrace   RET   ktrace 0
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/bin/wine"
 90037 ktrace   RET   execve -1 errno 2 No such file or directory
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/sbin/wine"
 90037 ktrace   RET   execve -1 errno 2 No such file or directory
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/usr/bin/wine"
 90037 ktrace   RET   execve -1 errno 2 No such file or directory
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/usr/games/wine"
 90037 ktrace   RET   execve -1 errno 2 No such file or directory
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/usr/sbin/wine"
 90037 ktrace   RET   execve -1 errno 2 No such file or directory
 90037 ktrace   CALL  execve(0xbfbfe170,0xbfbfe698,0xbfbfe6a0)
 90037 ktrace   NAMI  "/usr/local/bin/wine"
 90037 ktrace   NAMI  "/libexec/ld-elf.so.1"

I'm a bit behind on the releases, but this just seem so odd regardless:
<escaflowne/p7> (79 ~): uname -a
FreeBSD escaflowne.ceyah.org 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Tue
Jun 20 11:19:53 EDT 2006
root at escaflowne.ceyah.org:/backup/obj/data/src/sys/ESCAFLOWNE  i386

Recompiling Wine makes no difference, and it is the only application on
my system that appears to be affected.  I'm using Wine 0.9.17,1.

I'm really stumped as to what the problem is.


More information about the freebsd-stable mailing list