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

Re: User for startupitem.executable

[Russell Jones]

Hi Javier,

grep -ril startupitem.executable 
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/ 
| xargs less


suggests that sudo -u is the way to do it if a program doesn't know how 
to drop privileges. If that doesn't work, I guess several ports have the 
same problem that you describe with su. sudo does fork a process per the 
man page, so they may do.


Russell

(sent to macports-dev)

On 17/09/16 16:12, Javier Alcázar wrote:

Hi people,

I'm creating a new Portfile with startupitem.executable, and wondering 
what is the best way to execute the command with a specific user.


I tried using "su -c executable args" but with this approach 
launchd ends up monitoring the "su" process instead of the "executable"


What would you recommend to do so launchd looks at the "executable" 
process?






Cheers


--
Javier


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


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