Issues after installing.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. typing "wine iexplore" or substituting iexplore with any program.

What is the expected output? What do you see instead?
I am expecting that a program will launch, but it returns with this error code:
http://pastebin.com/NeX02N8x

What version of the product are you using? On what operating system?
Wine-1.3.33 on Snow Leopard OS X 10.6.8

Please provide any additional information below.
I posted this on the WineHQ forums and was told by the maker of this script 
that I had to file the issue here. He also told that my DYLD library fallback 
environment variable is not set correctly. I have the following in my .bashrc:
PATH="${HOME}/wine/wine-1.3.33/bin:${PATH}"
DYLD_FALLBACK_LIBRARY_PATH="${HOME}/wine-1.3.33/lib:/usr/X11/lib:/usr/lib"

Original issue reported on code.google.com by skippe...@gmail.com on 2 Dec 2011 at 4:56

[GoogleCodeExporter]

Have you installed Xquartz?  If not, I would recommend doing so:

- http://xquartz.macosforge.org/

Please run these from a terminal and report the output:

echo ${DYLD_FALLBACK_LIBRARY_PATH}
echo ${PATH}
which freetype-config

This still looks like an issue with an incorrect $DYLD_FALLBACK_LIBRARY_PATH 
environment variable.

Original comment by rwoodsm...@gmail.com on 2 Dec 2011 at 5:44

• Changed state: Started

[GoogleCodeExporter]

> echo ${DYLD_FALLBACK_LIBRARY_PATH}
This doesn't return anything. Just a blank line.
> echo ${PATH}
/Users/Skip/wine/wine-1.3.33/bin:/Users/Skip/perl5/perlbrew/bin:/Users/Skip/perl
5/perlbrew/perls/perl-5.14.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/o
pt/X11/bin:/usr/local/git/bin:/usr/X11/bin:/usr/local/sbin
> which freetype-config
/usr/bin/config

I think it went wrong with that variable indeed.
Here's what I have set in my .bashrc:
DYLD_FALLBACK_LIBRARY_PATH="${HOME}/wine-1.3.33/lib:/usr/X11/lib:/usr/lib"

Thanks for your help.

Original comment by skippe...@gmail.com on 2 Dec 2011 at 9:09

[GoogleCodeExporter]

"echo ${DYLD_FALLBACK_LIBRARY_PATH}" should return something.  "which 
freetype-config" should not return /usr/bin/config - ever.  Something appears 
to be wrong with your system.  Log out, log back in (or reboot), start a new 
terminal and re-run the commands in the previous comment.  If they're still 
returning nothing/incorrect values, double check you have the latest Xcode for 
10.6, the latest Xquartz, and then attempt to rebuild Wine using the script. If 
you get errors during the build, post to pastebin and link them here. -r

Original comment by rwoodsm...@gmail.com on 3 Dec 2011 at 2:31

• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Ok so now I rebooted, and tried it with the default terminal and I get this:
> echo ${DYLD_FALLBACK_LIBRARY_PATH}
/Users/Skip/wine-1.3.33/lib:/usr/X11/lib:/usr/lib
> echo ${PATH}
/Users/Skip/wine/wine-1.3.33/bin:/Users/Skip/perl5/perlbrew/bin:/Users/Skip/perl
5/perlbrew/perls/perl-5.14.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/o
pt/X11/bin:/usr/local/git/bin:/usr/X11/bin:/usr/local/sbin
> which freetype-config
/Users/Skip/wine/wine-1.3.33/bin/freetype-config

Running these in iTerm2 results in the same. I think these are the correct 
results.

I tried the command "wine winecfg", it seems like it's trying to start up, but 
it never does anything.
ps aux | grep wine results in the following processes:

/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wine 
C:\windows\system32\plugplay.exe
/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wine 
C:\windows\system32\winedevice.exe MountMgr
/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wine 
C:\windows\system32\services.exe
/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wine 
C:\windows\system32\winemenubuilder.exe -a -r
/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wine 
C:\windows\system32\wineboot.exe --init
/Users/Skip/wine/wine-1.3.33/bin/../lib/../bin/wineserver
grep wine

My XQuartz also seems to start up and then shut down frequently.

Original comment by skippe...@gmail.com on 3 Dec 2011 at 1:08

[GoogleCodeExporter]

Do you have Xquartz 2.7.0 installed? If not, install it. If so, reinstall it. 
Logout/login or reboot afterward and make sure it's the default X server by 
running "xterm" from Terminal.app. You should get an Xquartz startup, not an 
X11.app startup. You can watch the system log from Console.app (in Applications 
-> Utilities).

Once Xquartz is verified working, do the following:

- Kill the default Wine prefix with:
cd ${HOME}
rm -rf .wine

- Fix your DYLD_FALLBACK_LIBRARY_PATH environment variable to point to Xquartz 
by adjusting it in your .bashrc/.bash_profile file:
export 
DYLD_FALLBACK_LIBRARY_PATH="${HOME}/wine-1.3.33/lib:/opt/X11/lib:/usr/X11/lib:/u
sr/lib"

Logout/log back in again (or reboot and verify the DYLD_FALLBACK_LIBRARY_PATH 
env var looks correct. Try "wine winecfg" again and it should be functional. If 
it doesn't work at this point, or Xquartz/X11 are broken, something else is 
royally screwed on your system. -r

Original comment by rwoodsm...@gmail.com on 4 Dec 2011 at 1:09

[GoogleCodeExporter]

Ok, winecfg starts up. But only if I do the command in my tiling window manager 
I have running under X. So only if I run the command in X, not in Terminal.
But as an example, winetricks firefox doesn't seem to work, it doesn't return 
with errors, however. When I run the command it creates an empty line, and then 
eventually shuts off XQuartz.
But we've made progression. :P
Again, thanks for your help.

Original comment by skipdesi...@live.nl on 4 Dec 2011 at 4:33

[GoogleCodeExporter]

Update: winetricks firefox now returns this error:

------------------------------------------------------
wine cmd.exe /c echo '%ProgramFiles%' returned unexpanded string 
'%ProgramFiles%' ... can be caused a corrupt wineprefix, an old wine, or by not 
owning /Users/Skip/.wine
------------------------------------------------------

Original comment by skipdesi...@live.nl on 4 Dec 2011 at 4:47

[GoogleCodeExporter]

Closing this. The problem is not with Wine, or osxwinebuild.sh, but likely with 
your window manager or some other modification you've made to OS X/X11.

Original comment by rwoodsm...@gmail.com on 4 Dec 2011 at 6:30

• Changed state: WontFix