Closed GoogleCodeExporter closed 9 years ago
Hey Ian, I'll check on this for you. I'm currently targeting 10.6 so that's my
build
environment, but I'll try to get a 10.5 build environment setup as soon as
possible.
What versions of the following are you using?
* Xcode
* GCC
You can check your Xcode version by opening it in Finder: Hard Disk ->
Developer ->
Applications -> Xcode.app. When the app's up, select Xcode -> About Xcode and
note
the version.
You can check which version of GCC is in use from the Terminal; in Finder: Hard
Disk
-> Applications -> Utilities -> Terminal.app. When your terminal is running,
grab
the GCC version and let me know what it is:
gcc --version
It will probably default to GCC 4.0. If you have GCC 4.2 available, it may be
possible to build Wine with 4.2. You can check to see if it's installed by
running:
gcc-4.2 --version
You can (possibly) force 4.2 by changing the lines in the script:
export CC="gcc"
export CXX="g++"
To:
export CC="gcc-4.2"
export CXX="g++-4.2"
Have previous builds worked for you as well? I added some optimizations
recently
that may be breaking the build.
Original comment by rwoodsm...@gmail.com
on 31 Mar 2010 at 3:49
I have reproduced this bug exactly once. I think you're actually hitting a
well-known, long-standing kernel
bug where Mach basically runs out of process/tasks/etc. and can't spin up new
processes. I only hit the
"Resource temporarily unavailable" error once, and this was after installing 3
versions of Xcode (2.5, 3.0, and
3.1.4) in /XcodeX.X.
I started a few looped builds on a freshly-booted Leopard machine using both
Xcode 3.0 and 3.1.4, all using
GCC 4.0 and all builds completed successfully. Kinda janky, but can you try
rebooting your machine, then
starting Terminal.app and re-running the build script?
Let me know how this goes.
Original comment by rwoodsm...@gmail.com
on 2 Apr 2010 at 3:22
Resolving - this appears to be the aforementioned kernel issue. A reboot
clears up the problem for me.
Original comment by rwoodsm...@gmail.com
on 7 Apr 2010 at 10:53
I was surprised to see this - it is EXACTLY what I ran into while attempting to
build
Wine. I was even more surprised that I followed the suggestion of rebooting the
machine, starting Terminal and trying it again ... when I ran the build script
following reboot; it didn't complete, but since it got farther, I tried it
another
time. Following the second reboot (and the third time of running the build
script),
it worked!?!
My configuration:
OSX 10.5.8
2.4Gz Core 2 Duo with 4Gb RAM
XCode 3.0
X11 2.3.3.2
Original comment by G4ph...@gmail.com
on 21 Apr 2010 at 10:06
Original issue reported on code.google.com by
ian.m.sm...@gmail.com
on 30 Mar 2010 at 9:16