Pavel Roskin wrote:
It is installed and it is run. If I replace wine-preloader with a script that logs the arguments and runs the renamed wine-preloader, I see it being called twice when an exe file with run with Wine. For example:
$ wine FarManager170.exe wine_main_preload_info not found wine_main_preload_info not found wine: could not load L"Z:\home\proski\dist\windows\FarManager170.exe": Invalid address
OK, it seems to be that the preloader can't lookup the ELF symbol "wine_main_preload_info" in wine-pthread.
That's bad, because the preloader is reserving memory, but has no way to let wine-pthread know which memory it reserved.
Can you see that symbol exported from wine-pthread?
mike@black:~/wine$ nm loader/wine-pthread | grep wine_main_preload_info 7bf023d8 B wine_main_preload_info
Also, which version of gcc/ld are you using? For me:
GNU ld version 2.17 Debian GNU/Linux gcc version 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)
Mike