On Jan 2, 2013, at 5:35 AM, Per Johansson wrote:
> On Wed, Jan 2, 2013 at 3:12 AM, Charles Davis wrote:
>
>> What kind of undefined symbol errors? Other than the ones I got because
>> as(1) from cctools can't grok CFI pseudo-ops (and probably never will
>> because of Clang), I don't know of a
On Wed, Jan 2, 2013 at 3:12 AM, Charles Davis wrote:
> What kind of undefined symbol errors? Other than the ones I got because as(1)
> from cctools can't grok CFI pseudo-ops (and probably never will because of
> Clang), I don't know of any symbol problems building Wine with Clang on Mac
> OS.
On Jan 1, 2013, at 4:36 PM, Per Johansson wrote:
> On Tue, Jan 1, 2013 at 7:11 PM, Per Johansson wrote:
>> On Tue, Jan 1, 2013 at 6:00 PM, Charles Davis 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 integr
On Tue, Jan 1, 2013 at 7:11 PM, Per Johansson wrote:
> On Tue, Jan 1, 2013 at 6:00 PM, Charles Davis 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
On Tue, Jan 1, 2013 at 6:00 PM, Charles Davis 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,
> th
On Jan 1, 2013, at 9:35 AM, Per Johansson wrote:
> Needed to build with clang on OS X, the normal as program can't parse clang
> output.
> It's a configure option since llvm-mc takes different options than the normal
> assembler, and on OS X is most often installed by a different name
> (llvm-mc-
