A new stable version of Wine (version 1.4) came out earlier this month. Is anyone hosting compiled Mac binaries for this version yet?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Wine 1.4
- Thread starter savvos
- Start date
- Sort by reaction score
Actually it kinda is.
You cannot build WINE through Xcode 4.2 or later. This is because Apple dropped support for GCC in 4.2, and your only option now is the LLVM-GCC compiler which seems to ignore several important compiler flags (they're there, they just don't do anything).
The end result is that any WINE compiled with Xcode 4.2 or later will immediately crash with an unhandled exception code. You cannot run anything, the resulting binaries are broken.
You will need to compile WINE with either: A) an Xcode version lower then 4.2, or B) a custom GCC compiler- probably something from Fink or Macports or something like that.
-SC
the latest stable release of wine is 1.5 not 1.4. maybe this release fixes the xcode compile problems mentioned?
you dont need to monkey with old versions of xcode to get GCC 4.2 either.
you dont need to monkey with old versions of xcode to get GCC 4.2 either.
cluthz
macrumors 68040
All 1.5.x releases are development releases, 1.4 is latest stable.
If you plan to run wine on OSX I suggest using Wineskin from www.doh123.com.
It has downloader for all recent wine and crossover binaries.
(from like 1.1.x to 1.5 including crossover 8 to 11.)
http://www.playonmac.com/en/news.html
Concerning gcc, I use OSX gcc packages from here:
http://r.research.att.com/tools/
They have gcc packages for xcode 4.2, I hope they also work for 4.3.
The apple llvm compiler is not fully compatible with code written for gcc. I highly doubt that there will be any fix from wine, since it is written for gcc.
Concerning gcc, I use OSX gcc packages from here:
http://r.research.att.com/tools/
They have gcc packages for xcode 4.2, I hope they also work for 4.3.
The apple llvm compiler is not fully compatible with code written for gcc. I highly doubt that there will be any fix from wine, since it is written for gcc.
As long as you do not want a Customized/patched Wine source... they stock Wine builds are already built and available for Wineskin, along with Crossover Wine versions too. There are also 3rd party customized engines available elsewhere for it (like at Portingteam.com).
I haven't had access to my build machine for a week, but I'll have a Wine 1.5 version up later today.
I haven't had access to my build machine for a week, but I'll have a Wine 1.5 version up later today.