> On 30 Aug 2021, at 6:30 am, Dave Horsfall wrote:
>>> Thanks for the heads-up; I think my MacBook Pro will be stuck forever on
>>> Sierra 10.12.6 (although admittedly I haven't tried High Sierra on this
>>> one) and MacPorts 2.6.3 is likely as far as it will go.
>
> I successfully installed
[ Late reply ]
On Thu, 12 Nov 2020, Mojca Miklavec wrote:
Thanks for the heads-up; I think my MacBook Pro will be stuck forever
on Sierra 10.12.6 (although admittedly I haven't tried High Sierra on
this one) and MacPorts 2.6.3 is likely as far as it will go.
I successfully installed High
On Nov 16, 2020, at 02:55, Dominik Reichardt wrote:
> Yes, everyone replying that you have the CLT installed, check if it’s
> actually the correct one. Because apparently there is a bug that makes Xcode
> report that the CLTs are installed *without* checking whether it is the
> correct
> On 16. Nov 2020, at 10:05, Wahlstedt Jyrki wrote:
>
>
>
>> Dominik Reichardt mailto:domi...@gmail.com>> kirjoitti
>> 16.11.2020 kello 10.55:
>>
>> In Xcode itself I actually do not see the CLT listed at all, only the
>> simulators.
>>
> I have mine here:
>
>
Indeed, there it is,
On 16/11/2020 02:56, Lothar Haeger wrote:
Same here: installing XCode and opening it once seems to install command line
tools. At least they are listed in Preferences as installed (at the same path
as XCode.app).
Seems as if no separate install is required with 12.x anymore.
Am 16.11.2020 um
> Same here: installing XCode and opening it once seems to install command line
> tools. At least they are listed in Preferences as installed (at the same path
> as XCode.app).
> Seems as if no separate install is required with 12.x anymore.
I’m agreeing with Ryan here.
Opening Xcode 12.2 did
Same here: installing XCode and opening it once seems to install command line
tools. At least they are listed in Preferences as installed (at the same path
as XCode.app).
Seems as if no separate install is required with 12.x anymore.
> Am 16.11.2020 um 06:41 schrieb Wahlstedt Jyrki :
>
>
>
> Ryan Schmidt kirjoitti 16.11.2020 kello 4.41:
>
> Hm. As far as I knew, the "components" that Xcode updates at first launch are
> only related to on-device iOS/iPadOS/watchOS/tvOS development.
Not 100 % sure, but entering the command gives:
jwa@bach:databases> xcode-select --install
Hm. As far as I knew, the "components" that Xcode updates at first launch are
only related to on-device iOS/iPadOS/watchOS/tvOS development.
> On Nov 15, 2020, at 20:39, John Chivian wrote:
>
> @Ryan - When I start Xcode after updating it tells me it is installing needed
> components, and
@Ryan - When I start Xcode after updating it tells me it is installing
needed components, and command line tools *is* one of the components
updated. It tells me that explicitly during the install. Again, the
"xcode-select install" is not something I've done manually either of the
last two
On Nov 15, 2020, at 16:53, John Chivian wrote:
> For me, every time Xcode is updated, the first time I start it following its
> update I am prompted to update components,
Yes.
> and the current version command line tools are installed.
No. "Components" are not "command line tools". You
My perception is that the "xcode-select --install" is not needed, as the
message below indicates. For me, every time Xcode is updated, the first
time I start it following its update I am prompted to update components,
and the current version command line tools are installed. Perhaps the
>
> % xcode-select --install
> xcode-select: error: command line tools are already installed, use "Software
> Update" to install updates
>
I did the following:
$ sudo rm -rf /Library/Developer/CommandLineTools
$ xcode-select —install
$ ls /Library/Developer/CommandLineTools/SDKs
MacOSX.sdk
* Ryan Schmidt:
> When you upgrade, PLEASE UPGRADE XCODE AND THE XCODE COMMAND LINE
> TOOLS. They are SEPARATE software packages that need to be updated
> SEPARATELY. It's in the migration instructions; please follow them.
As I have been bit by this issue (see
On Nov 11, 2020, at 10:06, Ryan Schmidt wrote:
> Apple has announced that macOS 11 Big Sur will be released tomorrow, November
> 12, 2020. In the coming days we will either release an installer for MacPorts
> 2.6.3 for macOS 11 or will release a new version of MacPorts with installers
> for
On Nov 11, 2020, at 22:27, Dave Horsfall wrote:
> On Wed, 11 Nov 2020, Ryan Schmidt wrote:
>
>> Apple has announced that macOS 11 Big Sur will be released tomorrow,
>> November 12, 2020. In the coming days we will either release an installer
>> for MacPorts 2.6.3 for macOS 11 or will
Thank you for the timely warning.
On Wed, Nov 11, 2020 at 10:06 AM Ryan Schmidt
wrote:
> Apple has announced that macOS 11 Big Sur will be released tomorrow,
> November 12, 2020. In the coming days we will either release an installer
> for MacPorts 2.6.3 for macOS 11 or will release a new
17 matches
Mail list logo