Closed GoogleCodeExporter closed 9 years ago
Nowhere near enough context. Please provide more output including the actual
error.
Original comment by rwoodsm...@gmail.com
on 7 Apr 2013 at 12:59
Hi !
This happens when the script starts executing the wine 1.5.27 build script.
What you see there "could not run 'make -j3' in
/Users/montyburns/wine/build/wine-1.5.27 - exiting" is all there is before
showing the command prompt. If there is a log file where to look for additional
error information, please let me know.
thanks in advance!
Original comment by chris...@gmail.com
on 7 Apr 2013 at 1:21
Re-run the script like this:
./osxwinebuild.sh 2>&1 | tee ./osxwinebuild.out
Attach the file "osxwinebuild.out" to this issue. -r
Original comment by rwoodsm...@gmail.com
on 7 Apr 2013 at 1:24
Hi,
thanks for your quick response, here's the redirected output file.
Christian.
Original comment by chris...@gmail.com
on 7 Apr 2013 at 2:15
Attachments:
It looks like an error with Clang, which AFAIK is only used for linking since
GCC is/should be built from source on 10.7+. Double check that there's a
gcc/g++ binary in /Users/montyburns/wine/tools/bin - if not, something else is
going on.
I'd also make sure you're running Xcode 4.6+, and have up-to-date command line
tools. You can open Xcode -> Preferences -> Downloads -> select Command Line
Tools.
I no longer have a 10.7 (or 10.8) machine to test on, so you may run into other
issues. Let me know if this helps at all! -r
Original comment by rwoodsm...@gmail.com
on 7 Apr 2013 at 2:35
Hi,
I do have a gcc/g++ binary in that folder, actually they're symlinks to
g++-apple-4.2 / gcc-apple-4.2. But.. my Xcode version is 4.5.2 ... and my
command-line tools seem to be outdated/not installed, so I'm going to download
them and see what happens, thanks once again for your quick response !
Christian.
Original comment by chris...@gmail.com
on 7 Apr 2013 at 2:52
It compiled just fine by downloading Xcode command-line tools.
thanks,
Original comment by chris...@gmail.com
on 7 Apr 2013 at 5:13
excellent! -r
Original comment by rwoodsm...@gmail.com
on 7 Apr 2013 at 6:47
Original issue reported on code.google.com by
chris...@gmail.com
on 7 Apr 2013 at 12:58