No Xcode 8 CLT for El Capitan

Adam Dershowitz dersh at alum.mit.edu
Thu Sep 22 20:10:30 PDT 2016



> On Sep 22, 2016, at 7:25 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
>> On Sep 22, 2016, at 3:44 AM, Jeremy Huddleston Sequoia <jeremyhu at macports.org> wrote:
>> 
>> 
>>> On Sep 21, 2016, at 12:15, Adam Dershowitz <dersh at alum.mit.edu> wrote:
>>> 
>>> That comment does not make it at all clear what those of us who updated to Xcode 8 (but not beta!) but are still on OS X 10.11 are supposed to do. 
>> 
>> If you don't need the CLTools, do nothing.
>> If you need the CLTools, install the latest version (or likely just stick with the version that you have if you already have them).
>> 
>>> I have posted a ticket about building cmake that seems to be because it is trying to use 10.12 SDK, but it is not clear how to work around that.
>> 
>> If a port is using an SDK and you haven't configure it to do so, that's a port bug.
>> 
>>> Perhaps the answer is to downgrade to Xcode 7, and stay away from 8?  (It is a big download!)
>> 
>> Why?  Fix the bug in the port.
>> 
>>> Or, it might be that just the 10.11 command line tools is enough?
>> 
>> The 10.11 CLTools installs the 10.11 headers to /.  Your issue with cmake is likely that the port is (incorrectly) trying to use the 10.12 SDK and expecting it to match the base system somehow... ?
> 
> cmake is a bug...
> 


A user just added a comment to the cmake issue that indicates that it is actually an undeclared type in the Apple header file, and that a bug report has now been filed with Apple.  It also includes a work around:  https://trac.macports.org/ticket/52258#comment:13 <https://trac.macports.org/ticket/52258#comment:13>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20160922/727f64ee/attachment.html>


More information about the macports-dev mailing list