Opened 2 years ago
Closed 2 years ago
#66064 closed defect (fixed)
installing on ventura still running after 2 hours...
| Reported by: | pidloop | Owned by: | admin@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | server/hosting | Version: | 2.8.0 |
| Keywords: | Cc: | ||
| Port: |
Description
Hello! I am currently running a fresh install using https://github.com/macports/macports-base/releases/download/v2.8.0/MacPorts-2.8.0-13-Ventura.pkg on a 2017 iMac running macOS 13.0 (Ventura) with 2 TB SSD and 64 GB RAM. It has been running now for over two hours, looks like there are two tclsh8.6 processes, one doing -selfupdate the other a portindex. Before running this, I performed the complete manual uninstall instructions at https://guide.macports.org/chunked/installing.macports.uninstalling.html.
Is something wrong or is this normal? Thanks for your help.
Change History (6)
comment:1 Changed 2 years ago by pidloop
comment:2 Changed 2 years ago by pidloop
Starting installing my favorite ports and it says I need Xcode 14.1. It doesn't seem to be out yet, newest I could find was 14.1.rc2 dated yesterday (Oct 24, today is 25). Seems a bit early to require 14.1.... is there a config file somewhere I can edit to allow using 14.0?
comment:3 Changed 2 years ago by pidloop
Close enough! After installing Xcode 14.1r2 I forgot to do the usual:
xcode-select —-install sudo xcodebuild -license
then when I install a port I get lots of these warnings:
Warning: The macOS 13 SDK does not appear to be installed
I went through the instructions at ProblemHotlist#reinstall-clt but I still get the warnings. Ports are installing ok so doesn't seem to be important.
Cheers!
comment:4 Changed 2 years ago by jmroot (Joshua Root)
- You would be generating the PortIndex locally on the first install at this stage, which can take quite a while.
- You need to install the 14.1 RC version of the Command Line Tools as well in order to get the macOS 13 SDK. https://developer.apple.com/download/all/?q=command%20line%20tools
comment:5 Changed 2 years ago by pidloop
Hah, that wasn't there yet when I went looking for xcode itself. Ok, got it. I moved 4.0.1 to /Applications/XCode-4.0.1.app and the 4.1 to /Applcations/Xcode.app. But then I found the paths were broken until I issued this bit of wizardry (which port kindly suggested!) :
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
and now everything is building with nary a complaint. Many thanks.
comment:6 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → server/hosting |
|---|---|
| Owner: | set to admin@… |
| Resolution: | → fixed |
| Status: | new → closed |
PortIndex files for Darwin 22 are now on the server.
Belay that. I went away and did something else for a while and came back to find it had completed successfully. Sorry to cry wolf. Many thanks for supporting Ventura.