On Tue, Jan 1, 2013 at 7:11 PM, Per Johansson <p...@morth.org> wrote: > On Tue, Jan 1, 2013 at 6:00 PM, Charles Davis <cdavi...@gmail.com> wrote: >> >> The right thing IMO is to test if we're compiling with Clang. If we are, >> then we should test if Clang is using its integrated assembler; if it is, >> then we should invoke Clang instead of the system assembler to assemble. >> This way, the user doesn't have to pass yet another option to configure in >> case he's using Clang. >> >> I have a patch to hack-fix winebuild to invoke Clang if we're being compiled >> by Clang; I can fix it to test for Clang and Clang's integrated assembler in >> configure and send it to the list--something I really should've done a while >> ago. > > Sure, sounds like a better plan. I tried briefly to use clang, but > there were a lot of undefined symbol errors I wasn't sure how to fix. > Tell me if you want some help with the patch. >
Btw, I should probably add that there's currently no way to build unpatched wine on 10.8 (and probably 10.7), as gcc-apple-4.2 get a conflict about cpu_type_t and pure gcc is not up to date with the latest Objective-C syntax in the system headers. Being able to build with clang would help a lot. Regards, -- Per Johansson
