Wine inside Xephyr on OSX
00cpxxx at gmail.com
Sat Apr 23 07:32:15 CDT 2016
On Sat, Apr 23, 2016 at 1:17 PM, Ken Thomases <ken at codeweavers.com> wrote:
> On Apr 23, 2016, at 4:59 AM, Henri Verbeet <hverbeet at gmail.com> wrote:
>> It could also be a library path issue. The easiest way to work around
>> it might be DYLD_FALLBACK_LIBRARY_PATH, although I'm sure there should
>> be actual OS X users on this list with more experience there.
> Yes, but it's potentially complicated.
> First, are you using XQuartz or another build of X.org (for example, from MacPorts)? You'd presumably want to point the library path to the libraries of the one you're using.
> I generally use XQuartz, so I do:
> export DYLD_FALLBACK_LIBRARY_PATH=/opt/X11/lib:/usr/lib
> The next question is whether you're running OS X 10.11 (El Capitan). If so, its System Integrity Protection feature will make a nuisance of itself. For security, it strips all DYLD_* variables from the environment when you run a "protected" executable. All system executables are protected, including the shell interpreters. If you are invoking a shell script such as the "wine" script for running Wine from the build tree, then that variable will be stripped. For that particular case, you can put the export command into a .winewrapper file to have it sourced by the shell, which will work. For other cases, you may need to edit your script.
Thanks you both, using the export worked as expected, and yes this is
XQuartz (installed from brew I guess, the computer is not mine). It is
running Yosemite so it was not a problem.
More information about the wine-devel