[cfe-dev] clang + compiler-rt aren't buildable on OS X since r157062; how to proceed?

[Jim Grosbach]

Daniel is the right person for that. We'll see what we can do.

A bit more context, FWIW. #1 is an option, but feels kinda rude to make that a hard requirement. It's available for anyone who wants to re-enable it locally, but we need something better for default use-cases. #2 doesn't quite work out, as it's not the deployment target that's the limiting factor in this scenario, but rather the version of the host-side tools. There's not a solid way to check those versions. #3 is viable as it isolates the public builds of supported open source targets from any weirdness of Apple side stuff.

-Jim

On May 31, 2012, at 4:50 PM, Nico Weber wrote:

> Cool. Could you work with someone who understands the compiler-rt
> build to make that happen and unbreak the build?
> 
> (I gave it a shot myself, but I'm not sure what the best way to go
> about things is. Maybe add a "platform = Darwin and $2 = ios then
> return" to compiler-rt/make/platform/clang_darwin.mk's CheckArches?)
> 
> Nico
> 
> On Thu, May 31, 2012 at 2:44 PM, Jim Grosbach <grosbach at apple.com> wrote:
>> #3.
>> 
>> On May 31, 2012, at 2:43 PM, Nico Weber <thakis at chromium.org> wrote:
>> 
>>> Hi,
>>> 
>>> r157062 broke bootstrap builds of clang if compiler-rt is built too.
>>> See http://llvm.org/PR12918 for details, in short: r157062 lets clang
>>> output a load command for iOS targets that the ar binary in all
>>> released Xcode versions doesn't understand. compiler-rt is built for
>>> mac and ios when compiling on OS X by default.
>>> 
>>> As a result, I haven't been able to push a new clang to the chromium
>>> repo in a while. What's the way forward here?
>>> 
>>> 1.) Make a prerelease ar a requirement for doing bootstrap builds for
>>> building clang and compiler-rt
>>> 
>>> 2.) Augment r157062 to only use new load commands if target platforms
>>> are new enough
>>> 
>>> 3.) Remove ios from the default compiler-rt build
>>> 
>>> 4.) Something else
>>> 
>>> 
>>> I'm not able to push new clang binaries to chromium until this is resolved.
>>> 
>>> Thanks,
>>> Nico
>>