[Bug 38380] OSX Wine64 compile hangs on /dlls/ntdll/relay.c with gcc4.9

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=38380

--- Comment #2 from Josh DuBois <duboisj at codeweavers.com> ---
Ken suggested the attached patches, which allow wine to compile with macports
gcc 4.8 on my OS X 10.9.5 box.  I am still in the process of testing, but it
runs at least notepad (and relay logging seems to work OK, so the modified
assembly works to that extent).

For what it's worth, these failures:  

{standard input}:1409:suffix or operands invalid for `movq'

... appear to be caused by a known bug in Apple's assembler.  The as I have in
/usr/bin reports:

duboisj:Downloads duboisj$ as -v
Apple Inc version cctools-855, GNU assembler version 1.38

and an as installed from macports reports:

duboisj:Downloads duboisj$ /opt/local/bin/as -v
Apple Inc version cctools-845, GNU assembler version 1.38

Both of these suffer from failure to assemble the movq instructions which
attempt to move from "normal" registers to the xmm0-3 registers.  I wasn't able
to find any assembler for OS X which did not suffer from the problem.  GCC
itself appears to have encountered the problem as well, calling the problem a
lack of "interunit movq" support in the assembler, as documented in these bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65306

Note that you will also have to disable the mac driver by passing 
--disable-winemac.drv to configure, because there are Objective-C features
which the mac driver uses which are only supported by clang.  (You won't need
to hack your /usr/include/dispatch/object.c that way).  You can still run
things with X11 even with the mac driver disabled.

The attached patch should apply on top of winehq
d15ca4edb9c3823a698c4bb6137c8777e1ad08dd.  (The configure changes are unrelated
to the movq problem, but still needed).  I think the only alternative is to
compile your own clang using the patches Charles Davis posted to wine-devel in
January or February 2015, and that seems likely to be hard since it's been a
while and they may not apply cleanly anymore.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.