wine users - Apr 2011 - Tring to Build Wine from Source on OS X

So I'm attempting to build Wine from the the source files in the Git
repository.  After running ./configure I took note of the dependencies that were
missing and went about trying to download, build and install them.  I then
re-ran ./configure and it still couldn't find any of the libraries I had
just downloaded.  My initial thought was that Macports was building the
libraries as 64-bit.  I changed the settings to build 32-bit/64-bit universal
binaries, and then uninstalled and reinstalled all the ports.  No change.  I
then moved over to Fink, thinking perhaps there was a problem with Macports,
checking first that Fink defaults to building 32-bit binaries.  Still no change.
I donwloaded the source files for libjpeg off the net (not through Macports or
Fink), and ran ./configure, make CFLAGS="-m32"
CXXFLAGS="-m32", make build, and make install clean.  This also
didn't work.  I freely admit that I'm at the bleeding edge of my
apptitude (the compilier flags are probably well beyond, I simply copied what I
thought was the appropriate commands after some Googling).  Any help on what
steps I'm missing/executing incorrectly would be greatly appreciated.

-JG

Did you remember to add your install paths to your environment before running
configure?

For example, if you built libjpeg with the following configure (I'm
presuming bash shell):


Code:
CFLAGS=-m32 LDFLAGS=-m32 configure --prefix=/usr/local/32bit
make
make install



Your configure line for wine would need to include the path to /usr/local/32bit:


Code:
CFLAGS=-I/usr/local/32bit/include LDFLAGS=/usr/local/32bit/lib configure



Depending what each package prefers to use for setting up its own headers and
libraries, you may need to include some or all of the following environment
variables:

CFLAGS=-I/usr/local/32bit/include
LDFLAGS=-L/usr/local/32bit/lib
PATH=${PATH}:/usr/local/32bit/bin
PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/usr/local/32bit/lib/pkgconfig

of course /usr/local/32bit is just an example. You could use whatever else you
prefer.

On Sun, Apr 24, 2011 at 11:26 PM, JimGross <wineforum-user at winehq.org>
wrote:
> So I'm attempting to build Wine from the the source files in the Git
repository. ?After running ./configure I took note of the dependencies that were
> missing and went about trying to download, build and install them. ?I then
re-ran ./configure and it still couldn't find any of the libraries I had
just
> downloaded. ?My initial thought was that Macports was building the
libraries as 64-bit. ?I changed the settings to build 32-bit/64-bit universal
> binaries, and then uninstalled and reinstalled all the ports.
That will not work.  The binaries have to be 32 bit.
> ?No change. ?I then moved over to Fink, thinking perhaps there was a
problem with Macports, checking first that Fink defaults to building 32-bit
> binaries.
They do.
However, what is missing is the pointers to where MacPorts (/opt/bin,
/opt/lib, /opt/include) or Fink (/sw/bin, /sw/lib, /sw/include)
>Still no change. ?I donwloaded the source files for libjpeg off the net (not
through Macports or Fink), and ran ./configure, make CFLAGS="-m32"
> CXXFLAGS="-m32", make build, and make install clean. ?This also
didn't work. ?I freely admit that I'm at the bleeding edge of my
apptitude (the
> compilier flags are probably well beyond, I simply copied what I thought
was the appropriate commands after some Googling). ?Any help on what
> steps I'm missing/executing incorrectly would be greatly appreciated.
>
In most cases you will need to tell the installer that you are using
an i386, not an i686 (64 bit Intel processor).

You will also ned to set the location of where the binaries, libraries
and includes are located at.  Both MacPorts and Fink build a complete
wine build.  I have been able to fake out Fink when I use a patched
wine file by just packaging up the git directory into a named bzip'd
tarball (tar jcf wine-1.3.18.tar.bz2 wine-git/* will do the job) and
then putting the tarball in the /sw/src directory.  When Fink chokes
on the mismatch of md5s, I tell the installer to ignore the mismatch
and no further problems resulted.  I have a shiny, new patched file.

Good luck Jim.

I'm not sure this is 100% correct... but something like this... might have
to edit some of the Path stuff if I have it wrong for your set up... but I'm
assuming most of the stuff you've built is off Macports and /opt/local...

do this in a new Terminal session


Code:
export
DYLD_FALLBACK_LIBRARY_PATH="/opt/local/lib:/usr/lib:/opt/X11/lib:/usr/X11/lib"
export CC="gcc-4.0"
export CXX="g++-4.0"
export CPPFLAGS="-I/opt/local/include"
export CFLAGS="-arch i386 -m32 -O2 ${CPPFLAGS}"
export CXXFLAGS="$CFLAGS"
export LDFLAGS="-L/opt/local/lib"



then try the configure.... thats similar to how I have the build script in
custom Wineskin builds to work.

Charles Davis wrote:
> On 4/25/11 10:14 AM, doh123 wrote:
> 
> > export CC="gcc-4.0"
> > export CXX="g++-4.0"
> > 
> If you're on Snow Leopard, you should use gcc-4.2 instead of 4.0:
> 
> export CC=gcc-4.2
> export CXX=g++-4.2
> 
> Chip

oops.. your right... I always default back to 4.0 cuz I build 10.5+ builds  :-)

Jim, I have a script that builds Wine and dependencies from source on OS X:

http://code.google.com/p/osxwinebuilder/

It has a lot of the compiler options necessary for building 32-bit on OS X if
you want to peruse the script. -r

On Mon, Apr 25, 2011 at 10:18 AM, rwoodsmall <wineforum-user at
winehq.org> wrote:
> Jim, I have a script that builds Wine and dependencies from source on OS X:
>
> http://code.google.com/p/osxwinebuilder/
>
> It has a lot of the compiler options necessary for building 32-bit on OS X
if you want to peruse the script. -r
>
I have your script.  Would you be acceptable for comments/questions on
it (off list and off forum of course)?
James McKenzie