Can't install wine on osx 10.6.4

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
cvknage
Newbie
Newbie
Posts: 2
Joined: Tue Aug 24, 2010 9:51 am

Can't install wine on osx 10.6.4

Post by cvknage »

Hi, I am new to all this wine stuff, and I am having some problems building wine following the official instructions (http://wiki.winehq.org/MacOSX/Building)

I have the latest version of Xcode installed and have X11 sitting in my Utilities folder as well.

I want to build wine from source without the use of MacPorts of Fink as I want to add the DIB Engine to my build.

however I can neither ./configure --verbose wine (with no patches), as I get the following message:

Code: Select all

configure: error: X 32-bit development files not found. Wine will be built
without X support, which probably isn't what you want. You will need to install
32-bit development packages of Xlib/Xfree86 at the very least.
Use the --without-x option if you really want this.
nor apply the DIB Engine patch as I get an error applying the first patch file..

Code: Select all

computer:wine user$ sudo patch -p1 < /usr/local/dibpatch/wineps-drv-send-page-size.patch
patching file dlls/wineps.drv/escape.c
Hunk #1 FAILED at 47.
Hunk #2 FAILED at 82.
Hunk #3 FAILED at 515.
Hunk #4 FAILED at 536.
4 out of 4 hunks FAILED -- saving rejects to file dlls/wineps.drv/escape.c.rej
I would greatly appreciate if someone can help me with this :-)
doh123
Level 8
Level 8
Posts: 1227
Joined: Tue Jul 14, 2009 1:21 pm

Post by doh123 »

compiling is a pain in the butt.... getting all the dependencies and paths set up... you have some X11 stuff not in your path. I made a script I use when I build that automatically makes a bundle for Wineskin, so I haven't done a build by hand in awhile... but you should probably look at setting a DYLD_FALLBACK_LIBRARY_PATH statement, which I think was on the wiki still.

That said, the dib engine doesn't work on Mac OS X... I don't think its supposed to, and I have tried it several times.
James Mckenzie

Can't install wine on osx 10.6.4

Post by James Mckenzie »

doh123 <[email protected]> wrote
Sent: Aug 24, 2010 9:30 PM
To: [email protected]
Subject: [Wine] Re: Can't install wine on osx 10.6.4
[snip]
That said, the dib engine doesn't work on Mac OS X... I don't think its supposed to, and I have tried it several times.
It will not, for now. The assembly code needs to be 'tweaked' to work with MacOSX. This is one of the many reasons the DIB code is not in Wine, yet.

James McKenzie
cvknage
Newbie
Newbie
Posts: 2
Joined: Tue Aug 24, 2010 9:51 am

Post by cvknage »

Hi guys, firstly thanks for replying :-)

James McKenzie:
It will not, for now. The assembly code needs to be 'tweaked' to work with MacOSX. This is one of the many reasons the DIB code is not in Wine, yet.

I understand..

I guess when doh123 can't make it work, my plan of making a game work by making a custom CXG 8.0.0 witn added DIB Engine Wineskin Engine is not going to happen anytime soon then..

doh123:
but you should probably look at setting a DYLD_FALLBACK_LIBRARY_PATH statement, which I think was on the wiki still.
I am not 100% sure what that means, nor how to do that.. I ran the commands:

Code: Select all

export CFLAGS="-arch i386 -m32"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="-I/usr/X11/include"
export LDFLAGS="-L/usr/X11/lib"
if that is what you mean? :) :)
User avatar
dimesio
Moderator
Moderator
Posts: 13373
Joined: Tue Mar 25, 2008 10:30 pm

Post by dimesio »

cvknage wrote: doh123:
but you should probably look at setting a DYLD_FALLBACK_LIBRARY_PATH statement, which I think was on the wiki still.
I am not 100% sure what that means, nor how to do that..
I think he means this: http://wiki.winehq.org/MacOSX/Building# ... 8fd8e53004
doh123
Level 8
Level 8
Posts: 1227
Joined: Tue Jul 14, 2009 1:21 pm

Post by doh123 »

cvknage wrote: I guess when doh123 can't make it work, my plan of making a game work by making a custom CXG 8.0.0 witn added DIB Engine Wineskin Engine is not going to happen anytime soon then..

doh123:
but you should probably look at setting a DYLD_FALLBACK_LIBRARY_PATH statement, which I think was on the wiki still.
I am not 100% sure what that means, nor how to do that.. I ran the commands:

Code: Select all

export CFLAGS="-arch i386 -m32"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="-I/usr/X11/include"
export LDFLAGS="-L/usr/X11/lib"
if that is what you mean? :) :)
if your using Wineskin you don't have to worry about any of it... everything is set. The build script I have makes an engine (Wine + Xquartz), all you need is the Wine source. You could also edit the build script to see what its doing if you'd like, its just bash.... it handles cxwine slightly different which has to be done because codeweavers changes some stuff to work with Crossover that isn't really good for general wine usage... primary wineboot.exe.so can't create a wineprefix in their build, because they have their own tools that make their "bottles". the WS4 based engine build script handles all that for you though.

if its not Wineskin those flags are needed, if your using Apple's X11 in /usr/X11... you might have to change it if your X11 is elsewhere.... normal Xquartz install should be /opt/X11, which I would recommend and never use Apple's X11.

as for DYLD_FALLBACK_LIBRARY_PATH, this is a environment variable OSX uses to find libraries in if they aren't found in the normal location a program is looking in. It unlikely this is part of your problem looking at it more, it affect runtime more than compile time problems... but I throw the kitchen sink at compiles just to make sure it has anything it might need.

In the Wineskin build script I have a line that says...

Code: Select all

export DYLD_FALLBACK_LIBRARY_PATH="$BEPATHLIBS:$OSXSDK/usr/lib"
in this example $BEPATHLIBS is the lib folder containing all libs of Wine's deps as well as all of Xquartz dylibs and deps. $OSXSDK/usr/lib shouldn't be needed unless you building for an OS version different than the one your on like Wineskin does. you can enter as many paths as you want within the quotes, just separate them all by colons.... just like normal $PATH.

back to your original post...
the DIB engine patch is failing on cxwine source because its just too different. you probably need to open the patch and apply it manually looking through the code.

The compile is failing probably because your Apple X11 files do not really have any 32 bit devel files.... installing the latest Xquartz and making your CPPFLAGS and LDFLAGS look at /opt/X11 instead of /usr/X11 might take care of that.
Locked