Ah, but I did download the RC2 versions of both; same problem.
On Sat, Oct 29, 2022 at 7:24 PM Ken Cunningham <[email protected]> wrote: > > Probably you need to go to the developer.apple.com website and download Xcode > 14.1 RC2 and the latest command line tools, and install those. > > Apple noted a last minute hiccup in Xcode that made them delay the final > Xcode 14.1 a bit, which is why Ventura is out but you can’t get the right > Xcode yet from the App Store. > > Everyone is in the same boat, homebrew too — shouldn’t be long. > > Ken > > > On Oct 29, 2022, at 4:56 PM, Kenneth Wolcott <[email protected]> wrote: > > So I downloaded and installed the XCode RC 2 and CL Tools R2.. > > Then > > port diagnose > Error: The installed version of Xcode, none, is not supported by > MacPorts. For your currently installed system, the following versions > of Xcode are supported: 14.1 > LaTeX: xcode-select --install > xcode-select: error: command line tools are already installed, use > "Software Update" in System Settings to install updates > > What does this mean? > > Ken Wolcott > > On Sat, Oct 29, 2022 at 4:45 PM Kenneth Wolcott > <[email protected]> wrote: > > > Hi; > > Interesting note: > > port diagnose > Error: The installed version of Xcode, none, is not supported by > MacPorts. For your currently installed system, the following versions > of Xcode are supported: 14.1 > > So I'm installing XCode and CLI tools again.. > > Thanks, > Ken Wolcott > > On Sat, Oct 29, 2022 at 1:57 PM Kenneth Wolcott > <[email protected]> wrote: > > > Thanks for the help; but still not working. > > sudo port clean qt5-qtbase > sudo port -v -t install qt5-qtbase > > failed. > > sudo port -v -t clean denemo > sudo port -v -t install denemo > > failed as above. > > sudo port selfupdate > sudo port upgrade outdated > > sudo port clean qt5-qtbase > sudo port clean denemo > sudo port -v -t install qt5-qtbase > > failed as above. > > Attached is the most recent log. > > Thanks, > Ken Wolcott > > On Sat, Oct 29, 2022 at 10:04 AM Ken Cunningham > <[email protected]> wrote: > > > should be fixed now, after you update > > thx K > >
