wine-devel @1.5.23: invalid operand for instruction lretw

[adamb2903]

This failed, despite fixing some missing dependancies (zenity, libnotify not required by default) and despite cleaning before attempting a rebuild. Logfile is attached. The important details are here:

:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"

[ryandesign (Ryan Carsten Schmidt)]

The important details are actually:

:info:build avifile.ucbCvr.s:443:2: error: invalid operand for instruction
:info:build         lretw
:info:build         ^
:info:build avifile.ucbCvr.s:580:2: error: invalid operand for instruction
:info:build         lretw
:info:build         ^
:info:build winebuild: /usr/bin/clang failed with status 1

I see this too on my Lion machine with Xcode 4.3.3, and one (or two?) of our buildbots experienced this as well. It built fine on my Mountain Lion machine with Xcode 4.6.

The problem seems to be that the version of Clang that you have doesn't like to build this part of Wine. What version of Clang do you have? Run "clang -v" to find out. What version of Xcode do you have? Run "xcodebuild -version" to find out.

It is strange that the Wine build is using Clang at all; it should be using only GCC 4.2, since the port says "compiler.whitelist gcc-4.2 apple-gcc-4.2". I must investigate this.

[ja_macports@…]

Same problem here with XCode 4.6 and clang -v returns "Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)"

[larryv (Lawrence Velázquez)]

Replying to ja_macports@…:

Same problem here with XCode 4.6 and clang -v returns "Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)"

If you have Xcode 4.6, you should have Apple LLVM Compiler 4.2. Please update your Command Line Tools from Xcode Preferences.

[ja_macports@…]

Replying to larryv@…:

Replying to ja_macports@…:

Same problem here with XCode 4.6 and clang -v returns "Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)"

If you have Xcode 4.6, you should have Apple LLVM Compiler 4.2. Please update your Command Line Tools from Xcode Preferences.

Thanks that works, Apple is really getting unintuitive on this.

Apple notes that: "Before installing, note that from within Terminal you can use the XCRUN tool to launch compilers and other tools embedded within the Xcode application. Use the XCODE-SELECT tool to define which version of Xcode is active. Type "man xcrun" from within Terminal to find out more."

So maybe port should be using XCRUN instead.

[raina@…]

Replying to ja_macports@…:

Replying to larryv@…:

Replying to ja_macports@…: If you have Xcode 4.6, you should have Apple LLVM Compiler 4.2. Please update your Command Line Tools from Xcode Preferences.

Thanks that works, Apple is really getting unintuitive on this.

Being a huge noob and awaiting for some official word on whether it's safe to update to 4.6, I tried this on Xcode 4.5.2. Updating the Command Line Tools does indeed work here as well and wine-devel 1.5.23 built alright.

[larryv (Lawrence Velázquez)]

Replying to raina@…:

Being a huge noob and awaiting for some official word on whether it's safe to update to 4.6, I tried this on Xcode 4.5.2. Updating the Command Line Tools does indeed work here as well and wine-devel 1.5.23 built alright.

“Official word” is probably not forthcoming. For what it’s worth, I’ve had no problems with 4.6, nor have I heard of any issues from any of the other MacPorts developers.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ja_macports@…:

So maybe port should be using XCRUN instead.

Discussions about changing the way MacPorts finds the compilers it uses should be directed to the macports-dev list. For now, we require the command line tools to be installed and up-to-date.

Replying to raina@…:

[...] awaiting for some official word on whether it's safe to update to 4.6, [...]

Discussions about whether Xcode 4.6 is suitable for general use should be directed to the macports-users list. It works fine for me though.

[ryandesign (Ryan Carsten Schmidt)]

Here is the upstream bug report about this problem: ​http://bugs.winehq.org/show_bug.cgi?id=32872

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #37955.

[ryandesign (Ryan Carsten Schmidt)]

r102696