probono probono@puredarwin.org writes:
However, with WINE, this does not work. My guess is that WINE launches other WINE instances through other mechanisms in the background, which in turn don't get loaded using the specified "$HERE/lib32/ld-linux.so.2" and --library-path "$HERE/lib32"
1.) Can you confirm? 2.) Is there any way to tell WINE to use a private, bundled ld-linux.so.2 (and related glibc and other libraries) instead of looking for it in the host system?
It's not possible in standard Wine, but you could probably hack wine_exec_wine_binary() in libs/wine/config.c to add your special magic.