Hi,
I’m running MacPorts 2.7.2 on Big Sur 11.6.5 with Xcode 12.5.1. I have put off
upgrading to Xcode 13 so far, but I would like to upgrade soon because I
understand that there are some security fixes in the latest Xcode 13.x that are
not available for Xcode 12.
Are there any issues to be
I believe the problem is that these two commands are not the same:
xcrun -sdk macosx –show-sdk-path
xcrun -sdk macosx -show-sdk-path
The first is what you ran, and the second is what you meant to run.
Right before show-sdk-path, I believe you used the wrong character (some sort
of dash instead
I was busy doing the first tests for macOS 12.3 and ran into this one:
% xcrun -sdk macosx –show-sdk-path
2022-04-16 18:49:47.763 xcodebuild[85239:384046] Requested but did not find
extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications
for extension
The following ports and their dependencies could be installed by me on macOS
12.3:
The following ports are currently installed:
certbot @1.26.0_0+python310 (active)
clamav-server @0.101.2_4+sanesecurity+scan_schedule_access (active)
dcc @2.3.168_0 (active)
dovecot @2.3.17_0+apns+solr
Hi,
On Sat, Apr 16, 2022 at 03:16:21PM +0200, Gerben Wierda via macports-users
wrote:
> I’m about to take the plunge and move one of my systems to macOS 12.3
> (which removes /usr/bin/python). I am going to consider that a
> MacPorts major migration (so following the migration instructions).
>
* Ralph Seichter via macports-users:
> I'm running a combination of macOS 12.3.1 and MacPorts 2.7.2 on an
> Intel-based MacBook Pro without any problems.
It is also worth mentioning that I use this machine for a lot of Python
software development. Works just fine.
-Ralph
* Gerben Wierda via macports-users:
> I’m about to take the plunge and move one of my systems to macOS 12.3
> (which removes /usr/bin/python). I am going to consider that a
> MacPorts major migration (so following the migration instructions).
I'm running a combination of macOS 12.3.1 and
One of the Mac I manage is on 12.3 (M1 processor). I’ve made a fresh MacPorts
installation, and installed the usual packages needed for our environment. Must
say that we don’t do any Python ourselves there, but several Python packages
are installed as dependencies in the process, and all
I’m about to take the plunge and move one of my systems to macOS 12.3 (which
removes /usr/bin/python). I am going to consider that a MacPorts major
migration (so following the migration instructions).
I haven’t seen any traffic on this issue. Does that mean hardly anyone is on
12.3? Is anyone
Hi,
On Thu, Apr 14, 2022 at 04:10:26PM -0500, Ryan Schmidt wrote:
> On Apr 14, 2022, at 14:34, Daniel J. Luke wrote:
> > Once you do step 2, the port command works again (and you should
> > follow the rest of the instructions, but if you're prepared to live
> > with the consequences of things
10 matches
Mail list logo
