Compiling Wine on Mac OS X 10.8.2?

[Jeremiah Flerchinger]

Is anyone compiling Wine from the git repository for OS X version 10.8.2?
At first I thought I broke my toolchain and could no longer compile Wine at
all, but this is not the case. I can still compile old releases, but can no
longer compile from git.

I'm just curious if anyone else has tried...

[Saulius Krasuckas]

* On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> Is anyone compiling Wine from the git repository for OS X version 
> 10.8.2?

Not me...
> At first I thought I broke my toolchain and could no longer compile Wine 
> at all, but this is not the case. I can still compile old releases, but 
> can no longer compile from git.

... but I would try running a regression test (git bisect) in your case.

S.

[Charles Davis]

On Feb 3, 2013, at 10:50 AM, Saulius Krasuckas wrote:
> * On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> > Is anyone compiling Wine from the git repository for OS X version 
> > 10.8.2?
>
> Not me...
> > At first I thought I broke my toolchain and could no longer compile Wine 
> > at all, but this is not the case. I can still compile old releases, but 
> > can no longer compile from git.
>
> ... but I would try running a regression test (git bisect) in your case.
> Why do I get the feeling that when you do, you'll end up at commit c14bdaf?

How exactly does it break?

Chip
> S.

[Bill Broach]

Which version of gcc are you compiling it with?

Im able to compile no issue with: i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)

On Feb 3, 2013, at 3:58 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> On Feb 3, 2013, at 10:50 AM, Saulius Krasuckas wrote:
> > * On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> > > Is anyone compiling Wine from the git repository for OS X version 
> > > 10.8.2?
> >
> > Not me...
> > > At first I thought I broke my toolchain and could no longer compile Wine 
> > > at all, but this is not the case. I can still compile old releases, but 
> > > can no longer compile from git.
> >
> > ... but I would try running a regression test (git bisect) in your case.
> > Why do I get the feeling that when you do, you'll end up at commit c14bdaf?
>
> How exactly does it break?
>
> Chip
> > S.

[Jeremiah Flerchinger]

Apple's GCC 4.2.1 version 5666.3



commdlg.vqed9R.s:259:2: error: invalid operand for instruction
        lrecompobj.IYZvhS.st:w
 1037 : 2 :  error:  invalid operand for instruction
 ^
        lretw
        ^
compobj.IYZvhS.s:1150:2: error: invalid operand for instruction
        lretw
        ^
compobj.IYZvhS.s:1195:2: error: invalid operand for instruction
        lretw
        ^
compobj.IYZvhS.s:1204:2: error: invalid operand for instruction
        lretw
        ^
compobj.IYZvhS.s:1213:2: error: invalid operand for instruction
        lretw
        ^
compobj.IYZvhS.s:1222:2: error: invalid operand for instruction
        lretw
        ^
compobj.IYZvhS.s:1231:2: error: invalid operand for instruction
        lretw
        ^
winebuild: /usr/bin/clang failed with status 1
winegcc: ../../tools/winebuild/
winebuild failed
make[1]: *** [commdlg.dll16.so] Error 2
make: *** [dlls/commdlg.dll16] Error 2
make: *** Waiting for unfinished jobs....
../../../tools/winegcc/winegcc -m32 -B../../../tools/winebuild
--sysroot=../../..  -s -Wb,-F,credui_test.exe  credui.o         testlist.o
-o credui_test-stripped.exe.so ../../../libs/port/libwine_port.a -lcredui
-L/Users/jeremiah/wine/wine-git/lib  -L/opt/X11/lib -framework CoreServices
-lz -L/opt/X11/lib -lGL -lGLU
winebuild: /usr/bin/clang failed with status 1
winegcc: ../../tools/winebuild/winebuild failed
make[1]: *** [compobj.dll16.so] Error 2
make: *** [dlls/compobj.dll16] Error 2
echo "credui_test.exe TESTRES \"credui_test-stripped.exe.so\"" |
../../../tools/wrc/wrc --nostdinc --po-dir=../../../po -m32 -I. -I.
-I../../../include -I../../../include  -DWINE_STRICT_PROTOTYPES
-DWINE_NO_NAMELESS_EXTENSION -DWIDL_C_INLINE_WRAPPERS   -o
../../../programs/winetest/credui_test.res
could not run 'make -j3' in /Users/jeremiah/wine/build/wine-git - exiting


On Sun, Feb 3, 2013 at 11:02 PM, Bill Broach <while1eq1.lists(a)gmail.com>wrote:
> Which version of gcc are you compiling it with?
>
> Im able to compile no issue with: i686-apple-darwin11-gcc-4.2.1 (GCC)
> 4.2.1 (Apple Inc. build 5666) (dot 3)
>
> On Feb 3, 2013, at 3:58 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> > On Feb 3, 2013, at 10:50 AM, Saulius Krasuckas wrote:
> > > * On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> > > > Is anyone compiling Wine from the git repository for OS X version
> > > > 10.8.2?
> > >
> > > Not me...
> > > > At first I thought I broke my toolchain and could no longer compile
>
> Wine
> > > > at all, but this is not the case. I can still compile old releases, but
> > > > can no longer compile from git.
> > >
> > > ... but I would try running a regression test (git bisect) in your case.
> > > Why do I get the feeling that when you do, you'll end up at commit
> > > c14bdaf?
> >
> > How exactly does it break?
> >
> > Chip
> > > S.

[Charles Davis]

On Feb 4, 2013, at 10:27 AM, Jeremiah Flerchinger wrote:
> Apple's GCC 4.2.1 version 5666.3
>
> commdlg.vqed9R.s:259:2: error: invalid operand for instruction
>         lrecompobj.IYZvhS.st:w
>  1037 : 2 :  error:  invalid operand for instruction 
>  ^
>         lretw
>         ^
> compobj.IYZvhS.s:1150:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1195:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1204:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1213:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1222:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1231:2: error: invalid operand for instruction
>         lretw
>         ^
> winebuild: /usr/bin/clang failed with status 1
> winegcc: ../../tools/winebuild/
> winebuild failed
> make[1]: *** [commdlg.dll16.so] Error 2
> make: *** [dlls/commdlg.dll16] Error 2
> make: *** Waiting for unfinished jobs....
> ../../../tools/winegcc/winegcc -m32 -B../../../tools/winebuild --sysroot=../../..  -s -Wb,-F,credui_test.exe  credui.o         testlist.o -o credui_test-stripped.exe.so ../../../libs/port/libwine_port.a -lcredui  -L/Users/jeremiah/wine/wine-git/lib  -L/opt/X11/lib -framework CoreServices -lz -L/opt/X11/lib -lGL -lGLU 
> winebuild: /usr/bin/clang failed with status 1
> winegcc: ../../tools/winebuild/winebuild failed
> make[1]: *** [compobj.dll16.so] Error 2
> make: *** [dlls/compobj.dll16] Error 2
> echo "credui_test.exe TESTRES \"credui_test-stripped.exe.so\"" |  ../../../tools/wrc/wrc --nostdinc --po-dir=../../../po -m32 -I. -I. -I../../../include -I../../../include  -DWINE_STRICT_PROTOTYPES -DWINE_NO_NAMELESS_EXTENSION -DWIDL_C_INLINE_WRAPPERS   -o ../../../programs/winetest/credui_test.res
> could not run 'make -j3' in /Users/jeremiah/wine/build/wine-git - exiting
> Yep, this is related to my patch alright.

I'm willing to bet you're still running Xcode 4.5, too. Try upgrading to 4.6.

Chip
> On Sun, Feb 3, 2013 at 11:02 PM, Bill Broach <while1eq1.lists(a)gmail.com> wrote:
> Which version of gcc are you compiling it with?
>
> Im able to compile no issue with: i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
>
> On Feb 3, 2013, at 3:58 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> > On Feb 3, 2013, at 10:50 AM, Saulius Krasuckas wrote:
> > > * On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> > > > Is anyone compiling Wine from the git repository for OS X version
> > > > 10.8.2?
> > >
> > > Not me...
> > > > At first I thought I broke my toolchain and could no longer compile Wine
> > > > at all, but this is not the case. I can still compile old releases, but
> > > > can no longer compile from git.
> > >
> > > ... but I would try running a regression test (git bisect) in your case.
> > > Why do I get the feeling that when you do, you'll end up at commit c14bdaf?
> >
> > How exactly does it break?
> >
> > Chip
> > > S.

[Jeremiah Flerchinger]

Chip,

I'm compiling from wine-git again. I had to install the new command line
tools for 4.6 and then reboot, since XCode 4.6 didn't seem to be enough.

It seems an odd behavior that the patches appeared to force winebuild to
use clang, when it had been using gcc before. Thanks and I'll try to see
if  can switch entirely to clang in my toolchain now.

J


On Mon, Feb 4, 2013 at 9:32 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> On Feb 4, 2013, at 10:27 AM, Jeremiah Flerchinger wrote:
>
> Apple's GCC 4.2.1 version 5666.3
>
> commdlg.vqed9R.s:259:2: error: invalid operand for instruction
>         lrecompobj.IYZvhS.st:w
>  1037 : 2 :  error:  invalid operand for instruction
>  ^
>         lretw
>         ^
> compobj.IYZvhS.s:1150:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1195:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1204:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1213:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1222:2: error: invalid operand for instruction
>         lretw
>         ^
> compobj.IYZvhS.s:1231:2: error: invalid operand for instruction
>         lretw
>         ^
> winebuild: /usr/bin/clang failed with status 1
> winegcc: ../../tools/winebuild/
> winebuild failed
> make[1]: *** [commdlg.dll16.so] Error 2
> make: *** [dlls/commdlg.dll16] Error 2
> make: *** Waiting for unfinished jobs....
> ../../../tools/winegcc/winegcc -m32 -B../../../tools/winebuild
> --sysroot=../../..  -s -Wb,-F,credui_test.exe  credui.o         testlist.o
> -o credui_test-stripped.exe.so ../../../libs/port/libwine_port.a
> -lcredui  -L/Users/jeremiah/wine/wine-git/lib  -L/opt/X11/lib -framework
> CoreServices -lz -L/opt/X11/lib -lGL -lGLU
> winebuild: /usr/bin/clang failed with status 1
> winegcc: ../../tools/winebuild/winebuild failed
> make[1]: *** [compobj.dll16.so] Error 2
> make: *** [dlls/compobj.dll16] Error 2
> echo "credui_test.exe TESTRES \"credui_test-stripped.exe.so\"" |
> ../../../tools/wrc/wrc --nostdinc --po-dir=../../../po -m32 -I. -I.
> -I../../../include -I../../../include  -DWINE_STRICT_PROTOTYPES
> -DWINE_NO_NAMELESS_EXTENSION -DWIDL_C_INLINE_WRAPPERS   -o
> ../../../programs/winetest/credui_test.res
> could not run 'make -j3' in /Users/jeremiah/wine/build/wine-git - exiting
>
> Yep, this is related to my patch alright.
>
> I'm willing to bet you're still running Xcode 4.5, too. Try upgrading to
> 4.6.
>
> Chip
>
> On Sun, Feb 3, 2013 at 11:02 PM, Bill Broach <while1eq1.lists(a)gmail.com>wrote:
> > Which version of gcc are you compiling it with?
> >
> > Im able to compile no issue with: i686-apple-darwin11-gcc-4.2.1 (GCC)
> > 4.2.1 (Apple Inc. build 5666) (dot 3)
> >
> > On Feb 3, 2013, at 3:58 PM, Charles Davis <cdavis5x(a)gmail.com> wrote:
> > > On Feb 3, 2013, at 10:50 AM, Saulius Krasuckas wrote:
> > > > * On Sun, 3 Feb 2013, Jeremiah Flerchinger wrote:
> > > > > Is anyone compiling Wine from the git repository for OS X version
> > > > > 10.8.2?
> > > >
> > > > Not me...
> > > > > At first I thought I broke my toolchain and could no longer compile
> >
> > Wine
> > > > > at all, but this is not the case. I can still compile old releases,
> > > > > but
> > > > > can no longer compile from git.
> > > >
> > > > ... but I would try running a regression test (git bisect) in your
> > > > case.
> > > > Why do I get the feeling that when you do, you'll end up at commit
> > > > c14bdaf?
> > >
> > > How exactly does it break?
> > >
> > > Chip
> > > > S.

[Per Johansson]

On Sun, Feb 3, 2013 at 4:59 PM, Jeremiah Flerchinger
<jeremiah.flerchinger(a)gmail.com> wrote:
> Is anyone compiling Wine from the git repository for OS X version 10.8.2? At
> first I thought I broke my toolchain and could no longer compile Wine at
> all, but this is not the case. I can still compile old releases, but can no
> longer compile from git.
>
> I'm just curious if anyone else has tried...

Hi,

the default gcc binary hasn't been able to correctly compile wine
since 10.7 was released (since it was then switched to llvm-gcc).
clang should be able to compile latest master (since
http://source.winehq.org/git/wine.git/commit/c14bdaf1ddb7d0e5587f63f1216b61c...).
The only other option I'm aware of is gcc-apple-4.2 from macports.

Regards,
-- 
Per Johansson

[Jeremiah Flerchinger]

I was using a bash script from
http://code.google.com/p/osxwinebuilder/that downloaded and installed
gcc (not llvm-gcc) to compile Wine with that.
I edited the script to compile from the wine-git repository, which it did
perfectly on 10.8.2 until this past week.

I'll have to check the regression, but maybe I'll also try not using gcc to
see if Wine can compile using the default compiler from Apple now.


On Mon, Feb 4, 2013 at 8:29 AM, Per Johansson <per(a)morth.org> wrote:
> On Sun, Feb 3, 2013 at 4:59 PM, Jeremiah Flerchinger
> <jeremiah.flerchinger(a)gmail.com> wrote:
> > Is anyone compiling Wine from the git repository for OS X version
> > 10.8.2? At
> > first I thought I broke my toolchain and could no longer compile Wine at
> > all, but this is not the case. I can still compile old releases, but can
> > no
> > longer compile from git.
> >
> > I'm just curious if anyone else has tried...
>
> Hi,
>
> the default gcc binary hasn't been able to correctly compile wine
> since 10.7 was released (since it was then switched to llvm-gcc).
> clang should be able to compile latest master (since
>
> http://source.winehq.org/git/wine.git/commit/c14bdaf1ddb7d0e5587f63f1216b61c...
> ).
> The only other option I'm aware of is gcc-apple-4.2 from macports.
>
> Regards,
> --
> Per Johansson