[LLVMdev] [PATCH]: enable multilib build on x86_64-apple-darwin

Chris Lattner clattner at apple.com
Thu Aug 27 17:46:39 PDT 2009


On Aug 26, 2009, at 2:11 PM, Jack Howarth wrote:

> Any chance that we could get r80071 applied to llvm-gcc-2.4 2.6
> branch in about a week? As Mike said this change should be
> very safe.

Yes, I'll ask Tanya to pull it into the release.

-Chris

>             Jack
>
> On Wed, Aug 26, 2009 at 12:48:15AM -0700, Eric Christopher wrote:
>>
>> On Aug 25, 2009, at 9:57 PM, Chris Lattner wrote:
>>
>>>
>>> On Aug 25, 2009, at 2:33 PM, Mike Stump wrote:
>>>
>>>> On Aug 23, 2009, at 11:36 AM, Jack Howarth wrote:
>>>>> Current llvm-gcc-4.2 for trunk and the 2.6 release
>>>>> is unable to build the i386 multilib for the
>>>>> x86_64-apple-darwin target. The attached patch provides
>>>>> this support. Can we get this into the 2.6 release
>>>>> and trunk?
>>>>
>>>> This is fine.  I don't have a rw llvm-gcc tree, some else want to
>>>> check it in?  For 2.6, that's be someone else's call, for what it's
>>>> worth, this should be fairly safe.
>>>
>>> I applied this as r80071.  However, I don't understand what this
>>> does.  I'm able to build a working i386/x86-64 compiler on darwin
>>> without this, what exactly does this fix?  What exactly is an "i386
>>> multilib" and why do we care? :)
>>
>> If you build a native 64-bit darwin compiler (host/target are x86_64-
>> darwin) this will give you a -m32 multilib that will enable you to
>> target i386. Otherwise you have to build a 32-bit compiler that has a
>> 64-bit multilib.
>>
>> -eric
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev




More information about the llvm-dev mailing list