http://bugs.winehq.org/show_bug.cgi?id=34739
--- Comment #4 from Austin English austinenglish@gmail.com 2013-10-17 05:23:22 CDT --- (In reply to comment #3)
(In reply to comment #2)
OK, I understand: misexec is in fact a shell script that calls the wine executable. So,
It's not a shell script but a Windows executable that exists in both 32-bit and 64-bit flavors in a Wow64 build.
I believe this problem occurs when someone starts a 32-bit winelib program on a 64-bit prefix from the command line or a script, so maybe we should just print a helpful warning message.
Yes, please. It's a very common problem.
On that note, why does 'wine foo.exe' default to the 32-bit binary before the 64-bit binary, when in a 64-bit prefix? Why not: wine32 -> 'wine32' wine64 -> 'wine64' wine -> 'wine64', if 64-bit prefix, else just 'wine'
I've searched around a bit, but haven't found an explanation.