Re: No Xcode 8 CLT for El Capitan

[Christopher Jones]

> 
> 
> 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 
> 

That bug report is referring to the header /usr/local/include/pthread.h …. 
Apple did not ship that file…

> 
> 
> 
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org 
> https://lists.macosforge.org/mailman/listinfo/macports-dev 
> 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

> On Sep 22, 2016, at 7:25 AM, Ryan Schmidt  wrote:
> 
> 
>> On Sep 22, 2016, at 3:44 AM, Jeremy Huddleston Sequoia 
>>  wrote:
>> 
>> 
>>> On Sep 21, 2016, at 12:15, Adam Dershowitz  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 




___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Ryan Schmidt]

> On Sep 22, 2016, at 9:19 AM, Adam Dershowitz  wrote:
> 
> Perhaps the answer, that I was missing, is that to use Xcode 8, on 10.11, the 
> user must explicitly install CLTools, but that would not be the case to run 
> Xcode 7 on 10.11 or Xcode 8 on 10.12?

On every version of the Mac operating system ever made, to use any version of 
MacPorts ever made, you should install Xcode and the command line tools. It 
would be nice if we did not require both, but we currently do, because some 
ports will fail to build when one or the other is not present. Though if you 
use a default MacPorts installation and can therefore receive binaries from our 
server, you may be able to avoid those problems since you won't have to build 
most ports yourself.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 22, 2016, at 12:32, Adam Dershowitz  wrote:
> 
> 
> 
>> On Sep 22, 2016, at 3:24 PM, Jeremy Huddleston Sequoia 
>>  wrote:
>> 
>> 
>>> On Sep 22, 2016, at 10:37, Adam Dershowitz  wrote:
>>> 
>>> 
>>> 
 On Sep 22, 2016, at 1:07 PM, Jeremy Huddleston Sequoia 
  wrote:
 
> 
> On Sep 22, 2016, at 07:19, Adam Dershowitz  wrote:
> 
> 
> 
>> On Sep 22, 2016, at 4:49 AM, Jeremy Huddleston Sequoia 
>>  wrote:
>> 
>> 
>>> On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
>>> 
>>> It does:
>>> 
>>> $ xcode-select -p
>>> /Applications/Xcode.app/Contents/Developer
>>> 
>>> 
>>> For me some updates in Macports, including some builds, seem to work 
>>> OK, and others, such as cmake, are giving an error:
>>> https://trac.macports.org/ticket/52258
>>> 
>>> I’m not sure if I then need to completely switch to Xcode 7?  Or if I 
>>> can just install the command line tools for 10.11 Xcode 7.3.1?  If I do 
>>> that, where do they install, so that I can point xcode-select to the 
>>> proper path?
>> 
>> If you don't have the CLTools installed, you wouldn't be able to install 
>> most of MacPorts.  I'm pretty sure you likely have them installed.
>> 
>> Dropping back down to Xcode 7 would mean that Xcode.app would contain 
>> the 10.11 SDK and would workaround your issue, but the issue is that the 
>> port isn't honoring your SDK (and maybe deployment target) selections 
>> (which default to / and host os version respectively).
>> 
>> 
> 
> 
> Something is still not clear to me.  I had Xcode 7 installed.  I was 
> under the impression that it included the SDK internally, so I don’t 
> think that I had separately installed the CLTools (although I’m not 
> positive).  
 
 Do you have /usr/include on your system?  If you do, you installed the 
 CLTools.
>>> 
>>> Yes, I do.  Although I can’t confirm when I might have installed it (is 
>>> there an easy way to tell if the headers were from some older version i.e. 
>>> 10.7,10.8 etc?).
>> 
>> $ pkgutil --file-info /usr/include/AvailabilityInternal.h
>> 
>> or just:
>> 
>> $ grep 'define __MAC_OS_X_VERSION_MAX_ALLOWED' 
>> /usr/include/AvailabilityInternal.h
>> 
>> The OS upgrade should remove that path, so you likely installed it at some 
>> point since upgrading your OS.
> 
> I do have the 10.11 tools installed (although they are slightly different 
> from each other and from my current OS:
> 
> $ pkgutil --file-info /usr/include/AvailabilityInternal.h
> volume: /
> path: /usr/include/AvailabilityInternal.h
> 
> pkgid: com.apple.pkg.DevSDK
> pkg-version: 10.11.3.0.1.1456982112
> install-time: 1457024872
> uid: 0
> gid: 0
> mode: 644
> 
> pkgid: com.apple.pkg.DevSDK_OSX1011
> pkg-version: 7.3.1.0.1.1461711523
> install-time: 1462497081
> uid: 0
> gid: 0
> mode: 644
> $ grep 'define __MAC_OS_X_VERSION_MAX_ALLOWED' 
> /usr/include/AvailabilityInternal.h
>#define __MAC_OS_X_VERSION_MAX_ALLOWED __MAC_10_11_4
> 
> But, likely close enough.  


Yep, there were no SDK changes in 10.11.5 and 10.11.6, so there was no need to 
release SDK updates for those OS versions.

What you have there is exactly as expected.

> And, I have used macports for many years without a problem (over many 
> versions of Xcode).  When Xcode 8 was released I installed it, but didn’t 
> install CLTools either.
> What still isn’t clear to me is if cmake and openmodelica (which does 
> have the same problem as cmake, but it also depends on cmake so I tried 
> to build that with the working cmake) should work with my current 
> configuration?  Do they each have a bug?  Should just installing 10.11 
> CLTools allow them to build?
 
 It's possibly a bug in cmake and openmodelica ports (they're using the SDK 
 inside of Xcode.app even though MacPorts is configured to use /).
 
 It's definitely a bug in cmake and openmodelica upstream.  They're failing 
 to build properly for the older deployment targets when using newer SDKs.
>>> 
>>> In that case, it sounds likely that installing the newer CLTools won’t 
>>> help, since I already have /usr/include.  So, at this point my options are 
>>> to wait for bug fixes, or to downgrade.
>> 
>> Yes.
> 
> One other question.  As openmodelica uses cmake to build.  Is it likely that 
> the bug in cmake is also affecting openmodelica (cache, links, stored paths 
> etc)?  Or, instead is it more likely that each happens to have the identical 
> problem, independent of each other?

They are a bit independent.  It's more of a development paradigm shift.  With 
modern SDKs (like macOS, iOS, and I believe also Android and Windows), the SDK 
advertises support for the newest functionality 

Re: No Xcode 8 CLT for El Capitan

[Brandon Allbery]

On Thu, Sep 22, 2016 at 3:32 PM, Adam Dershowitz  wrote:

> One other question.  As openmodelica uses cmake to build.  Is it likely
> that the bug in cmake is also affecting openmodelica (cache, links, stored
> paths etc)?  Or, instead is it more likely that each happens to have the
> identical problem, independent of each other?


It's a bad system configuration test; as such, it affects both cmake's own
configuration and any program that uses cmake for configuration, as the
same faulty test will be used in both cases.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

> On Sep 22, 2016, at 3:24 PM, Jeremy Huddleston Sequoia 
>  wrote:
> 
> 
>> On Sep 22, 2016, at 10:37, Adam Dershowitz  wrote:
>> 
>> 
>> 
>>> On Sep 22, 2016, at 1:07 PM, Jeremy Huddleston Sequoia 
>>>  wrote:
>>> 
 
 On Sep 22, 2016, at 07:19, Adam Dershowitz  wrote:
 
 
 
> On Sep 22, 2016, at 4:49 AM, Jeremy Huddleston Sequoia 
>  wrote:
> 
> 
>> On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
>> 
>> It does:
>> 
>> $ xcode-select -p
>> /Applications/Xcode.app/Contents/Developer
>> 
>> 
>> For me some updates in Macports, including some builds, seem to work OK, 
>> and others, such as cmake, are giving an error:
>> https://trac.macports.org/ticket/52258
>> 
>> I’m not sure if I then need to completely switch to Xcode 7?  Or if I 
>> can just install the command line tools for 10.11 Xcode 7.3.1?  If I do 
>> that, where do they install, so that I can point xcode-select to the 
>> proper path?
> 
> If you don't have the CLTools installed, you wouldn't be able to install 
> most of MacPorts.  I'm pretty sure you likely have them installed.
> 
> Dropping back down to Xcode 7 would mean that Xcode.app would contain the 
> 10.11 SDK and would workaround your issue, but the issue is that the port 
> isn't honoring your SDK (and maybe deployment target) selections (which 
> default to / and host os version respectively).
> 
> 
 
 
 Something is still not clear to me.  I had Xcode 7 installed.  I was under 
 the impression that it included the SDK internally, so I don’t think that 
 I had separately installed the CLTools (although I’m not positive).
>>> 
>>> Do you have /usr/include on your system?  If you do, you installed the 
>>> CLTools.
>> 
>> Yes, I do.  Although I can’t confirm when I might have installed it (is 
>> there an easy way to tell if the headers were from some older version i.e. 
>> 10.7,10.8 etc?).
> 
> $ pkgutil --file-info /usr/include/AvailabilityInternal.h
> 
> or just:
> 
> $ grep 'define __MAC_OS_X_VERSION_MAX_ALLOWED' 
> /usr/include/AvailabilityInternal.h
> 
> The OS upgrade should remove that path, so you likely installed it at some 
> point since upgrading your OS.

I do have the 10.11 tools installed (although they are slightly different from 
each other and from my current OS:

$ pkgutil --file-info /usr/include/AvailabilityInternal.h
volume: /
path: /usr/include/AvailabilityInternal.h

pkgid: com.apple.pkg.DevSDK
pkg-version: 10.11.3.0.1.1456982112
install-time: 1457024872
uid: 0
gid: 0
mode: 644

pkgid: com.apple.pkg.DevSDK_OSX1011
pkg-version: 7.3.1.0.1.1461711523
install-time: 1462497081
uid: 0
gid: 0
mode: 644
$ grep 'define __MAC_OS_X_VERSION_MAX_ALLOWED' 
/usr/include/AvailabilityInternal.h
#define __MAC_OS_X_VERSION_MAX_ALLOWED __MAC_10_11_4

But, likely close enough.

> 
 And, I have used macports for many years without a problem (over many 
 versions of Xcode).  When Xcode 8 was released I installed it, but didn’t 
 install CLTools either.
 What still isn’t clear to me is if cmake and openmodelica (which does have 
 the same problem as cmake, but it also depends on cmake so I tried to 
 build that with the working cmake) should work with my current 
 configuration?  Do they each have a bug?  Should just installing 10.11 
 CLTools allow them to build?
>>> 
>>> It's possibly a bug in cmake and openmodelica ports (they're using the SDK 
>>> inside of Xcode.app even though MacPorts is configured to use /).
>>> 
>>> It's definitely a bug in cmake and openmodelica upstream.  They're failing 
>>> to build properly for the older deployment targets when using newer SDKs.
>> 
>> In that case, it sounds likely that installing the newer CLTools won’t help, 
>> since I already have /usr/include.  So, at this point my options are to wait 
>> for bug fixes, or to downgrade.
> 
> Yes.

One other question.  As openmodelica uses cmake to build.  Is it likely that 
the bug in cmake is also affecting openmodelica (cache, links, stored paths 
etc)?  Or, instead is it more likely that each happens to have the identical 
problem, independent of each other?

Again, thank you.


> 
 Perhaps the answer, that I was missing, is that to use Xcode 8, on 10.11, 
 the user must explicitly install CLTools, but that would not be the case 
 to run Xcode 7 on 10.11 or Xcode 8 on 10.12?
>>> 
>>> Depends on your perspective.  We'd like to be in the world where you don't 
>>> need to install the system headers, but 90% of OSS software fails when the 
>>> SDK is newer than the base system because most OSS assumes that the SDK 
>>> matches the minimum deployment target.
>> 
>> 
>> Thanks.
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 22, 2016, at 10:37, Adam Dershowitz  wrote:
> 
> 
> 
>> On Sep 22, 2016, at 1:07 PM, Jeremy Huddleston Sequoia 
>>  wrote:
>> 
>>> 
>>> On Sep 22, 2016, at 07:19, Adam Dershowitz  wrote:
>>> 
>>> 
>>> 
 On Sep 22, 2016, at 4:49 AM, Jeremy Huddleston Sequoia 
  wrote:
 
 
> On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
> 
> It does:
> 
> $ xcode-select -p
> /Applications/Xcode.app/Contents/Developer
> 
> 
> For me some updates in Macports, including some builds, seem to work OK, 
> and others, such as cmake, are giving an error:
> https://trac.macports.org/ticket/52258
> 
> I’m not sure if I then need to completely switch to Xcode 7?  Or if I can 
> just install the command line tools for 10.11 Xcode 7.3.1?  If I do that, 
> where do they install, so that I can point xcode-select to the proper 
> path?
 
 If you don't have the CLTools installed, you wouldn't be able to install 
 most of MacPorts.  I'm pretty sure you likely have them installed.
 
 Dropping back down to Xcode 7 would mean that Xcode.app would contain the 
 10.11 SDK and would workaround your issue, but the issue is that the port 
 isn't honoring your SDK (and maybe deployment target) selections (which 
 default to / and host os version respectively).
 
 
>>> 
>>> 
>>> Something is still not clear to me.  I had Xcode 7 installed.  I was under 
>>> the impression that it included the SDK internally, so I don’t think that I 
>>> had separately installed the CLTools (although I’m not positive).  
>> 
>> Do you have /usr/include on your system?  If you do, you installed the 
>> CLTools.
> 
> Yes, I do.  Although I can’t confirm when I might have installed it (is there 
> an easy way to tell if the headers were from some older version i.e. 
> 10.7,10.8 etc?).

$ pkgutil --file-info /usr/include/AvailabilityInternal.h

or just:

$ grep 'define __MAC_OS_X_VERSION_MAX_ALLOWED' 
/usr/include/AvailabilityInternal.h

The OS upgrade should remove that path, so you likely installed it at some 
point since upgrading your OS.

>>> And, I have used macports for many years without a problem (over many 
>>> versions of Xcode).  When Xcode 8 was released I installed it, but didn’t 
>>> install CLTools either.
>>> What still isn’t clear to me is if cmake and openmodelica (which does have 
>>> the same problem as cmake, but it also depends on cmake so I tried to build 
>>> that with the working cmake) should work with my current configuration?  Do 
>>> they each have a bug?  Should just installing 10.11 CLTools allow them to 
>>> build?
>> 
>> It's possibly a bug in cmake and openmodelica ports (they're using the SDK 
>> inside of Xcode.app even though MacPorts is configured to use /).
>> 
>> It's definitely a bug in cmake and openmodelica upstream.  They're failing 
>> to build properly for the older deployment targets when using newer SDKs.
> 
> In that case, it sounds likely that installing the newer CLTools won’t help, 
> since I already have /usr/include.  So, at this point my options are to wait 
> for bug fixes, or to downgrade.

Yes.

>>> Perhaps the answer, that I was missing, is that to use Xcode 8, on 10.11, 
>>> the user must explicitly install CLTools, but that would not be the case to 
>>> run Xcode 7 on 10.11 or Xcode 8 on 10.12?
>> 
>> Depends on your perspective.  We'd like to be in the world where you don't 
>> need to install the system headers, but 90% of OSS software fails when the 
>> SDK is newer than the base system because most OSS assumes that the SDK 
>> matches the minimum deployment target.
> 
> 
> Thanks.  



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

> On Sep 22, 2016, at 1:07 PM, Jeremy Huddleston Sequoia 
>  wrote:
> 
>> 
>> On Sep 22, 2016, at 07:19, Adam Dershowitz  wrote:
>> 
>> 
>> 
>>> On Sep 22, 2016, at 4:49 AM, Jeremy Huddleston Sequoia 
>>>  wrote:
>>> 
>>> 
 On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
 
 It does:
 
 $ xcode-select -p
 /Applications/Xcode.app/Contents/Developer
 
 
 For me some updates in Macports, including some builds, seem to work OK, 
 and others, such as cmake, are giving an error:
 https://trac.macports.org/ticket/52258
 
 I’m not sure if I then need to completely switch to Xcode 7?  Or if I can 
 just install the command line tools for 10.11 Xcode 7.3.1?  If I do that, 
 where do they install, so that I can point xcode-select to the proper path?
>>> 
>>> If you don't have the CLTools installed, you wouldn't be able to install 
>>> most of MacPorts.  I'm pretty sure you likely have them installed.
>>> 
>>> Dropping back down to Xcode 7 would mean that Xcode.app would contain the 
>>> 10.11 SDK and would workaround your issue, but the issue is that the port 
>>> isn't honoring your SDK (and maybe deployment target) selections (which 
>>> default to / and host os version respectively).
>>> 
>>> 
>> 
>> 
>> Something is still not clear to me.  I had Xcode 7 installed.  I was under 
>> the impression that it included the SDK internally, so I don’t think that I 
>> had separately installed the CLTools (although I’m not positive).
> 
> Do you have /usr/include on your system?  If you do, you installed the 
> CLTools.

Yes, I do.  Although I can’t confirm when I might have installed it (is there 
an easy way to tell if the headers were from some older version i.e. 10.7,10.8 
etc?).


> 
>> And, I have used macports for many years without a problem (over many 
>> versions of Xcode).  When Xcode 8 was released I installed it, but didn’t 
>> install CLTools either.
>> What still isn’t clear to me is if cmake and openmodelica (which does have 
>> the same problem as cmake, but it also depends on cmake so I tried to build 
>> that with the working cmake) should work with my current configuration?  Do 
>> they each have a bug?  Should just installing 10.11 CLTools allow them to 
>> build?
> 
> It's possibly a bug in cmake and openmodelica ports (they're using the SDK 
> inside of Xcode.app even though MacPorts is configured to use /).
> 
> It's definitely a bug in cmake and openmodelica upstream.  They're failing to 
> build properly for the older deployment targets when using newer SDKs.

In that case, it sounds likely that installing the newer CLTools won’t help, 
since I already have /usr/include.  So, at this point my options are to wait 
for bug fixes, or to downgrade.
> 
>> Perhaps the answer, that I was missing, is that to use Xcode 8, on 10.11, 
>> the user must explicitly install CLTools, but that would not be the case to 
>> run Xcode 7 on 10.11 or Xcode 8 on 10.12?
> 
> Depends on your perspective.  We'd like to be in the world where you don't 
> need to install the system headers, but 90% of OSS software fails when the 
> SDK is newer than the base system because most OSS assumes that the SDK 
> matches the minimum deployment target.



Thanks.


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

> On Sep 22, 2016, at 4:49 AM, Jeremy Huddleston Sequoia 
>  wrote:
> 
> 
>> On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
>> 
>> It does:
>> 
>> $ xcode-select -p
>> /Applications/Xcode.app/Contents/Developer
>> 
>> 
>> For me some updates in Macports, including some builds, seem to work OK, and 
>> others, such as cmake, are giving an error:
>> https://trac.macports.org/ticket/52258
>> 
>> I’m not sure if I then need to completely switch to Xcode 7?  Or if I can 
>> just install the command line tools for 10.11 Xcode 7.3.1?  If I do that, 
>> where do they install, so that I can point xcode-select to the proper path?
> 
> If you don't have the CLTools installed, you wouldn't be able to install most 
> of MacPorts.  I'm pretty sure you likely have them installed.
> 
> Dropping back down to Xcode 7 would mean that Xcode.app would contain the 
> 10.11 SDK and would workaround your issue, but the issue is that the port 
> isn't honoring your SDK (and maybe deployment target) selections (which 
> default to / and host os version respectively).
> 
> 


Something is still not clear to me.  I had Xcode 7 installed.  I was under the 
impression that it included the SDK internally, so I don’t think that I had 
separately installed the CLTools (although I’m not positive).  And, I have used 
macports for many years without a problem (over many versions of Xcode).  When 
Xcode 8 was released I installed it, but didn’t install CLTools either.
What still isn’t clear to me is if cmake and openmodelica (which does have the 
same problem as cmake, but it also depends on cmake so I tried to build that 
with the working cmake) should work with my current configuration?  Do they 
each have a bug?  Should just installing 10.11 CLTools allow them to build?

Perhaps the answer, that I was missing, is that to use Xcode 8, on 10.11, the 
user must explicitly install CLTools, but that would not be the case to run 
Xcode 7 on 10.11 or Xcode 8 on 10.12?




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Ryan Schmidt]

> On Sep 22, 2016, at 3:44 AM, Jeremy Huddleston Sequoia 
>  wrote:
> 
> 
>> On Sep 21, 2016, at 12:15, Adam Dershowitz  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...

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 13:44, Jack Howarth  wrote:
> 
> On Wed, Sep 21, 2016 at 4:19 PM, Rainer Müller  wrote:
>> On 2016-09-21 21:15, Adam Dershowitz 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.
>>> 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.
>> 
>> That would be normal. The latest SDK can be used on previous systems.
>> For example, on OS X 10.10 Yosemite, Xcode 7.2 also only ships the 10.11
>> SDK.
>> 
> 
> Though apparently not for the SDK installed in / by the Command Line
> Tools!  

The SDK installed at / needs to match the base system.  If you installed 10.12 
headers to /, projects would fail to link due to header / library mismatch.

> Otherwise, Apple wouldn't have declared that there will be no
> 10.11 Command Line Tools in the Xcode 8 releases and would have
> provided  a 10.11 Command Line Tools for Xcode 8.1 which installed the
> 10.12 SDK in /.

Apple never declared that.

The only thing stated is that there would be no release for Xcode 8 (ie, 8.0).

The issue that prompted us to not ship the tools was discovered very late in 
the 8.0 cycle and will take time to address.  We are aware of the problem and 
are working on a solution.

In the mean time, you should just use the 7.3 CLTools (for the SDK at /) and 
Xcode 8.0 for the toolchain.

--Jeremy

smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 13:02, Jack Howarth  wrote:
> 
> On Wed, Sep 21, 2016 at 3:46 PM, Marko Käning  wrote:
>> Hi,
>> 
>> there is no CLT for Xcode 8?
>> 
>> How come Xcode 8.0 tells me in "Preferences/Locations" that it uses CLT 
>> "Xcode 8.0 (8A218a)”!
>> 
> 
> Launching the Xcode 8 application should resolve the license issue.
> 
>> I recently ran into this issue
>> ---
>> :info:configure
>> :info:configureXcode not set up properly. You may need to confirm the 
>> license
>> :info:configureagreement by running /usr/bin/xcodebuild without 
>> arguments.
>> :info:configure
>> ---
>> with Xcode 8 on El-Capitan myself when trying to install port:qt5(-kde).
>> 
>> 
>> 
>> Qt’s configure script errors out because of a non-found xcrun:
> 
> The xcrun copy in Xcode.app has been deprecated out in favor of the
> system copy in /usr/bin.

Slight correction there... it was deprecated around Xcode 5.
It was removed in Xcode 8.

> Upstream qt development fixed this issue by changing the failing test
> for xcrun to one for xcodebuild.
> 
> https://trac.macports.org/ticket/52200
> 
>> ---
>> $ which xcrun
>> /usr/bin/xcrun
>> $ /usr/bin/xcrun -find xcrun
>> xcrun: error: unable to find utility "xcrun", not a developer tool or in PATH
>> ---
>> 
>> René thus suggested the attached patch for qt5(-kde) as a workaround .
>> 
>> Greets,
>> Marko
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 12:46, Marko Käning  wrote:
> 
> Hi,
> 
> there is no CLT for Xcode 8?
> 
> How come Xcode 8.0 tells me in "Preferences/Locations" that it uses CLT 
> "Xcode 8.0 (8A218a)”!

That refers to what is selected via xcode-select.  That means that xcrun and 
the stubs like /usr/bin/clang result in usage of the toolchains within that 
Xcode.app version.  The CLTools toolchain is in 
/Library/Developer/CommandLineTools.  If you have Xcode.app installed, you 
likely don't even care about /Library/Developer/CommandLineTools and the only 
reason you need the CLTools package is for the headers for the base system 
(/usr/include, et al.)


> 
> I recently ran into this issue 
> ---
> :info:configure
> :info:configureXcode not set up properly. You may need to confirm the 
> license
> :info:configureagreement by running /usr/bin/xcodebuild without arguments.
> :info:configure
> ---
> with Xcode 8 on El-Capitan myself when trying to install port:qt5(-kde).
> 
> 
> 
> Qt’s configure script errors out because of a non-found xcrun:
> ---
> $ which xcrun
> /usr/bin/xcrun
> $ /usr/bin/xcrun -find xcrun
> xcrun: error: unable to find utility "xcrun", not a developer tool or in PATH
> ---
> 
> René thus suggested the attached patch for qt5(-kde) as a workaround.
> 
> Greets,
> Marko
> 
> 
> 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 12:45, Adam Dershowitz  wrote:
> 
> It does:
> 
> $ xcode-select -p
> /Applications/Xcode.app/Contents/Developer
> 
> 
> For me some updates in Macports, including some builds, seem to work OK, and 
> others, such as cmake, are giving an error:
> https://trac.macports.org/ticket/52258
> 
> I’m not sure if I then need to completely switch to Xcode 7?  Or if I can 
> just install the command line tools for 10.11 Xcode 7.3.1?  If I do that, 
> where do they install, so that I can point xcode-select to the proper path?

If you don't have the CLTools installed, you wouldn't be able to install most 
of MacPorts.  I'm pretty sure you likely have them installed.

Dropping back down to Xcode 7 would mean that Xcode.app would contain the 10.11 
SDK and would workaround your issue, but the issue is that the port isn't 
honoring your SDK (and maybe deployment target) selections (which default to / 
and host os version respectively).



> 
> --Adam
> 
> 
> 
>> On Sep 21, 2016, at 3:40 PM, Jack Howarth  
>> wrote:
>> 
>> On Wed, Sep 21, 2016 at 3:15 PM, Adam Dershowitz  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.
>>> 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.
>>> Perhaps the answer is to downgrade to Xcode 7, and stay away from 8?  (It 
>>> is a big download!)
>>> Or, it might be that just the 10.11 command line tools is enough?
>>> 
>> 
>> If you install Xcode 8 on 10.11, you need to make sure that
>> 'xcode-select -p' reports /Applications/Xcode.app/Contents/Developer
>> so that you are actually using the Xcode 8 compilers. The Command Line
>> Tools installed by Software Update or 'xcode-select --install' on
>> 10.11 will be those from Xcode 7.3.1 and will provide the 10.11 SDK
>> installed in /.
>> 
>>> --Adam
>>> 
>>> 
>>> 
 On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  
 wrote:
 
 Jack Howarth has noted on IRC that that Apple will not be releasing
 a Command Line Tools package for Xcode 8 on El Capitan [*].
 
  There is no Command Line Tools (OS X 10.11) for Xcode
  8 package. Xcode 8 contains SDKs that are incompatible
  with earlier toolchains. Developers who want to make use
  of the Xcode 8 SDKs from the command line must choose
  the SDK with xcode-select. Developers on OS X El Capitan
  who have installed versions of the Command Line Tools
  (OS X 10.11) for Xcode 8 Beta should install Command
  Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
 
 Do we need to adjust our installation instructions to account for this?
 The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
 me; maybe it's not a problem at all.
 
 [*]: 
 http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
 
 vq
 ___
 macports-dev mailing list
 macports-dev@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-dev
>>> 
>>> ___
>>> macports-dev mailing list
>>> macports-dev@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 12:15, Adam Dershowitz  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... ?

> 
> --Adam
> 
> 
> 
>> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  wrote:
>> 
>> Jack Howarth has noted on IRC that that Apple will not be releasing
>> a Command Line Tools package for Xcode 8 on El Capitan [*].
>> 
>>  There is no Command Line Tools (OS X 10.11) for Xcode
>>  8 package. Xcode 8 contains SDKs that are incompatible
>>  with earlier toolchains. Developers who want to make use
>>  of the Xcode 8 SDKs from the command line must choose
>>  the SDK with xcode-select. Developers on OS X El Capitan
>>  who have installed versions of the Command Line Tools
>>  (OS X 10.11) for Xcode 8 Beta should install Command
>>  Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>> 
>> Do we need to adjust our installation instructions to account for this?
>> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
>> me; maybe it's not a problem at all.
>> 
>> [*]: 
>> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
>> 
>> vq
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jeremy Huddleston Sequoia]

> On Sep 21, 2016, at 11:44, Lawrence Velázquez  wrote:
> 
> Jack Howarth has noted on IRC that that Apple will not be releasing
> a Command Line Tools package for Xcode 8 on El Capitan [*].
> 
>   There is no Command Line Tools (OS X 10.11) for Xcode
>   8 package. Xcode 8 contains SDKs that are incompatible
>   with earlier toolchains. Developers who want to make use
>   of the Xcode 8 SDKs from the command line must choose
>   the SDK with xcode-select. Developers on OS X El Capitan
>   who have installed versions of the Command Line Tools
>   (OS X 10.11) for Xcode 8 Beta should install Command
>   Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
> 
> Do we need to adjust our installation instructions to account for this?
> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
> me; maybe it's not a problem at all.

No need to change any instructions for MacPorts.

Install the Xcode 7 CLT
Install Xcode 8.0
Everything will work the way you want.

The only reason that we have our users install the CLT package is for the SDK 
that is installed at /.  There is no difference between that content in the 
Xcode 7 CLT and what would have been the Xcode 8 CLT.

The only difference is that the Xcode 8 CLT would contain the Xcode 8 toolchain 
at /Library/Developer/CommandLineTools.  Unfortunately, this toolchain 
(specifically swift) is not compatible with the OS X 10.11 SDK, so we did not 
ship it and are working on a solution to the problem.

--Jeremy



smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jack Howarth]

On Wed, Sep 21, 2016 at 4:19 PM, Rainer Müller  wrote:
> On 2016-09-21 21:15, Adam Dershowitz 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.
>> 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.
>
> That would be normal. The latest SDK can be used on previous systems.
> For example, on OS X 10.10 Yosemite, Xcode 7.2 also only ships the 10.11
> SDK.
>

Though apparently not for the SDK installed in / by the Command Line
Tools!  Otherwise, Apple wouldn't have declared that there will be no
10.11 Command Line Tools in the Xcode 8 releases and would have
provided  a 10.11 Command Line Tools for Xcode 8.1 which installed the
10.12 SDK in /.

> Rainer
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[René J . V . Bertin]

On Wednesday September 21 2016 16:02:48 Jack Howarth wrote:

> Upstream qt development fixed this issue by changing the failing test
> for xcrun to one for xcodebuild.
...
> > René thus suggested the attached patch for qt5(-kde) as a workaround .

Great minds think alike? :)

R.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Rainer Müller]

On 2016-09-21 21:15, Adam Dershowitz 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. 
> 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.

That would be normal. The latest SDK can be used on previous systems.
For example, on OS X 10.10 Yosemite, Xcode 7.2 also only ships the 10.11
SDK.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jack Howarth]

On Wed, Sep 21, 2016 at 3:46 PM, Marko Käning  wrote:
> Hi,
>
> there is no CLT for Xcode 8?
>
> How come Xcode 8.0 tells me in "Preferences/Locations" that it uses CLT 
> "Xcode 8.0 (8A218a)”!
>

Launching the Xcode 8 application should resolve the license issue.

> I recently ran into this issue
> ---
> :info:configure
> :info:configureXcode not set up properly. You may need to confirm the 
> license
> :info:configureagreement by running /usr/bin/xcodebuild without arguments.
> :info:configure
> ---
> with Xcode 8 on El-Capitan myself when trying to install port:qt5(-kde).
>
>
>
> Qt’s configure script errors out because of a non-found xcrun:

The xcrun copy in Xcode.app has been deprecated out in favor of the
system copy in /usr/bin.
Upstream qt development fixed this issue by changing the failing test
for xcrun to one for xcodebuild.

https://trac.macports.org/ticket/52200

> ---
> $ which xcrun
> /usr/bin/xcrun
> $ /usr/bin/xcrun -find xcrun
> xcrun: error: unable to find utility "xcrun", not a developer tool or in PATH
> ---
>
> René thus suggested the attached patch for qt5(-kde) as a workaround .
>
> Greets,
> Marko
>
>
>
>
>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

> On Sep 21, 2016, at 3:44 PM, Lawrence Velázquez  wrote:
> 
>> On Sep 21, 2016, at 3:38 PM, Adam Dershowitz  wrote:
>> 
>> The release Xcode 8 release notes (no longer beta) don’t have that comment:
>> https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html
> 
> I think that only covers 8.0, not 8.1.
> 
> vq

Yes, that’s correct.  
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Marko Käning]

Hi,

there is no CLT for Xcode 8?

How come Xcode 8.0 tells me in "Preferences/Locations" that it uses CLT "Xcode 
8.0 (8A218a)”!

I recently ran into this issue 
---
:info:configure
:info:configureXcode not set up properly. You may need to confirm the 
license
:info:configureagreement by running /usr/bin/xcodebuild without arguments.
:info:configure
---
with Xcode 8 on El-Capitan myself when trying to install port:qt5(-kde).



Qt’s configure script errors out because of a non-found xcrun:
---
$ which xcrun
/usr/bin/xcrun
$ /usr/bin/xcrun -find xcrun
xcrun: error: unable to find utility "xcrun", not a developer tool or in PATH
---

René thus suggested the attached patch for qt5(-kde) as a workaround.

Greets,
Marko





patch-no-xcrun-f-xcrun.diff
Description: Binary data


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

It does:

$ xcode-select -p
/Applications/Xcode.app/Contents/Developer


For me some updates in Macports, including some builds, seem to work OK, and 
others, such as cmake, are giving an error:
https://trac.macports.org/ticket/52258 

I’m not sure if I then need to completely switch to Xcode 7?  Or if I can just 
install the command line tools for 10.11 Xcode 7.3.1?  If I do that, where do 
they install, so that I can point xcode-select to the proper path?

--Adam



> On Sep 21, 2016, at 3:40 PM, Jack Howarth  
> wrote:
> 
> On Wed, Sep 21, 2016 at 3:15 PM, Adam Dershowitz  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.
>> 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.
>> Perhaps the answer is to downgrade to Xcode 7, and stay away from 8?  (It is 
>> a big download!)
>> Or, it might be that just the 10.11 command line tools is enough?
>> 
> 
> If you install Xcode 8 on 10.11, you need to make sure that
> 'xcode-select -p' reports /Applications/Xcode.app/Contents/Developer
> so that you are actually using the Xcode 8 compilers. The Command Line
> Tools installed by Software Update or 'xcode-select --install' on
> 10.11 will be those from Xcode 7.3.1 and will provide the 10.11 SDK
> installed in /.
> 
>> --Adam
>> 
>> 
>> 
>>> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  wrote:
>>> 
>>> Jack Howarth has noted on IRC that that Apple will not be releasing
>>> a Command Line Tools package for Xcode 8 on El Capitan [*].
>>> 
>>>  There is no Command Line Tools (OS X 10.11) for Xcode
>>>  8 package. Xcode 8 contains SDKs that are incompatible
>>>  with earlier toolchains. Developers who want to make use
>>>  of the Xcode 8 SDKs from the command line must choose
>>>  the SDK with xcode-select. Developers on OS X El Capitan
>>>  who have installed versions of the Command Line Tools
>>>  (OS X 10.11) for Xcode 8 Beta should install Command
>>>  Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>>> 
>>> Do we need to adjust our installation instructions to account for this?
>>> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
>>> me; maybe it's not a problem at all.
>>> 
>>> [*]: 
>>> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
>>> 
>>> vq
>>> ___
>>> macports-dev mailing list
>>> macports-dev@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>> 
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Lawrence Velázquez]

> On Sep 21, 2016, at 3:38 PM, Adam Dershowitz  wrote:
> 
> The release Xcode 8 release notes (no longer beta) don’t have that comment:
> https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html

I think that only covers 8.0, not 8.1.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jack Howarth]

On Wed, Sep 21, 2016 at 3:15 PM, Adam Dershowitz  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.
> 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.
> Perhaps the answer is to downgrade to Xcode 7, and stay away from 8?  (It is 
> a big download!)
> Or, it might be that just the 10.11 command line tools is enough?
>

If you install Xcode 8 on 10.11, you need to make sure that
'xcode-select -p' reports /Applications/Xcode.app/Contents/Developer
so that you are actually using the Xcode 8 compilers. The Command Line
Tools installed by Software Update or 'xcode-select --install' on
10.11 will be those from Xcode 7.3.1 and will provide the 10.11 SDK
installed in /.

> --Adam
>
>
>
>> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  wrote:
>>
>> Jack Howarth has noted on IRC that that Apple will not be releasing
>> a Command Line Tools package for Xcode 8 on El Capitan [*].
>>
>>   There is no Command Line Tools (OS X 10.11) for Xcode
>>   8 package. Xcode 8 contains SDKs that are incompatible
>>   with earlier toolchains. Developers who want to make use
>>   of the Xcode 8 SDKs from the command line must choose
>>   the SDK with xcode-select. Developers on OS X El Capitan
>>   who have installed versions of the Command Line Tools
>>   (OS X 10.11) for Xcode 8 Beta should install Command
>>   Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>>
>> Do we need to adjust our installation instructions to account for this?
>> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
>> me; maybe it's not a problem at all.
>>
>> [*]: 
>> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
>>
>> vq
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

The release Xcode 8 release notes (no longer beta) don’t have that comment:
https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html
 


But, they do seem to be trying to build for 10.12 instead of 10.11.  


--Adam



> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  wrote:
> 
> Jack Howarth has noted on IRC that that Apple will not be releasing
> a Command Line Tools package for Xcode 8 on El Capitan [*].
> 
>   There is no Command Line Tools (OS X 10.11) for Xcode
>   8 package. Xcode 8 contains SDKs that are incompatible
>   with earlier toolchains. Developers who want to make use
>   of the Xcode 8 SDKs from the command line must choose
>   the SDK with xcode-select. Developers on OS X El Capitan
>   who have installed versions of the Command Line Tools
>   (OS X 10.11) for Xcode 8 Beta should install Command
>   Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
> 
> Do we need to adjust our installation instructions to account for this?
> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
> me; maybe it's not a problem at all.
> 
> [*]: 
> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
> 
> vq
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Lawrence Velázquez]

> On Sep 21, 2016, at 3:08 PM, C. R. Oldham  wrote:
> 
> For those of us on Sierra, is it OK to install the CLT for Xcode 8?

I would assume so, given that there's a Sierra package available.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Adam Dershowitz]

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. 
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.
Perhaps the answer is to downgrade to Xcode 7, and stay away from 8?  (It is a 
big download!)
Or, it might be that just the 10.11 command line tools is enough?

--Adam



> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez  wrote:
> 
> Jack Howarth has noted on IRC that that Apple will not be releasing
> a Command Line Tools package for Xcode 8 on El Capitan [*].
> 
>   There is no Command Line Tools (OS X 10.11) for Xcode
>   8 package. Xcode 8 contains SDKs that are incompatible
>   with earlier toolchains. Developers who want to make use
>   of the Xcode 8 SDKs from the command line must choose
>   the SDK with xcode-select. Developers on OS X El Capitan
>   who have installed versions of the Command Line Tools
>   (OS X 10.11) for Xcode 8 Beta should install Command
>   Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
> 
> Do we need to adjust our installation instructions to account for this?
> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
> me; maybe it's not a problem at all.
> 
> [*]: 
> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
> 
> vq
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[C. R. Oldham]

For those of us on Sierra, is it OK to install the CLT for Xcode 8?




On September 21, 2016 at 12:52:29 PM, Jack Howarth 
(howarth.at.macpo...@gmail.com) wrote:

You probably also want to note...

On OS X El Capitan, running Swift from the command line can fail if
any Command Line Tools (OS X 10.11) package is installed on the
system. (28234754)

Workaround: Execute Swift through from the command line using xcrun, .
Choose the macOS SDK using the -sdk. For example, the following
command compiles the file main.swift:

xcrun -sdk macosx swiftc main.swift

also from the Known Command Line Tools issues.
Jack
ps Wonder what you have to do to get Apple to unlock your Apple
developer account from moderation. I am still flummoxed that they
locked my account for reposting something from the release notes.

On Wed, Sep 21, 2016 at 2:44 PM, Lawrence Velázquez  wrote:
> Jack Howarth has noted on IRC that that Apple will not be releasing
> a Command Line Tools package for Xcode 8 on El Capitan [*].
>
> There is no Command Line Tools (OS X 10.11) for Xcode
> 8 package. Xcode 8 contains SDKs that are incompatible
> with earlier toolchains. Developers who want to make use
> of the Xcode 8 SDKs from the command line must choose
> the SDK with xcode-select. Developers on OS X El Capitan
> who have installed versions of the Command Line Tools
> (OS X 10.11) for Xcode 8 Beta should install Command
> Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>
> Do we need to adjust our installation instructions to account for this?
> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
> me; maybe it's not a problem at all.
>
> [*]: 
> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
>
> vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: No Xcode 8 CLT for El Capitan

[Jack Howarth]

You probably also want to note...

On OS X El Capitan, running Swift from the command line can fail if
any Command Line Tools (OS X 10.11) package is installed on the
system. (28234754)

Workaround: Execute Swift through from the command line using xcrun, .
Choose the macOS SDK using the -sdk. For example, the following
command compiles the file main.swift:

xcrun -sdk macosx swiftc main.swift

also from the Known Command Line Tools issues.
 Jack
ps Wonder what you have to do to get Apple to unlock your Apple
developer account from moderation. I am still flummoxed that they
locked my account for reposting something from the release notes.

On Wed, Sep 21, 2016 at 2:44 PM, Lawrence Velázquez  wrote:
> Jack Howarth has noted on IRC that that Apple will not be releasing
> a Command Line Tools package for Xcode 8 on El Capitan [*].
>
> There is no Command Line Tools (OS X 10.11) for Xcode
> 8 package. Xcode 8 contains SDKs that are incompatible
> with earlier toolchains. Developers who want to make use
> of the Xcode 8 SDKs from the command line must choose
> the SDK with xcode-select. Developers on OS X El Capitan
> who have installed versions of the Command Line Tools
> (OS X 10.11) for Xcode 8 Beta should install Command
> Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>
> Do we need to adjust our installation instructions to account for this?
> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
> me; maybe it's not a problem at all.
>
> [*]: 
> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf
>
> vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

No Xcode 8 CLT for El Capitan

[Lawrence Velázquez]

Jack Howarth has noted on IRC that that Apple will not be releasing
a Command Line Tools package for Xcode 8 on El Capitan [*].

There is no Command Line Tools (OS X 10.11) for Xcode
8 package. Xcode 8 contains SDKs that are incompatible
with earlier toolchains. Developers who want to make use
of the Xcode 8 SDKs from the command line must choose
the SDK with xcode-select. Developers on OS X El Capitan
who have installed versions of the Command Line Tools
(OS X 10.11) for Xcode 8 Beta should install Command
Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)

Do we need to adjust our installation instructions to account for this?
The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
me; maybe it's not a problem at all.

[*]: 
http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev