Sequoia is very early (and MacPorts support for it may be incomplete or minimally tested, as the Xcode detection issues suggest). I usually run most of my systems at least one OS major release behind for at least a few months, or only run them earlier or run betas in an expendable (just re-create as needed) VM for testing.
> On Sep 17, 2024, at 01:34, Kenneth Wolcott <[email protected]> wrote: > > Hi; > > I can't remember all steps that I took, but all I know now is that I > have a really confused MacPorts status. > > First of all, I updated to the new MacOS, 15.0 (Sequoia). > > Secondly, I think I selected the update to the Command line tools, > which showed up after the OS update completed. > > Then I tried to download and install xCode v16. Everything > ***seemed*** fine at this point. > > I then ran sudo port migrate, and things went belly up. > > current state: > > following <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>: > > pkgutil > --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo} > 2>/dev/null | sed -n 's/^version: //p' > 16.0.0.0.1.1724870825 > > but > > sudo port diagnose > Password: > Warning: No Xcode version info was found for your OS version. > Warning: The Xcode Command Line Tools package appears to be installed, > but its receipt appears to be missing. > Warning: The Command Line Tools may be outdated, which can cause problems. > Warning: Please see: > <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt> > > I tried many times to install, uninstall, install, upgrade various > ports. Many fail, (especially low-level dependencies that most ports > require), looks like the tools are not visible... > > I'm stuck in a loop. > > Do I completely do a de-install of MacPorts? But even then, that > won't solve the problem(s) with the SDK and Command Line tools... > > I was wondering if I should wait until longer update the OS, but I > thought I would go ahead... > > I had issues that I wanted to resolve with arm symbols not found > when running some of the ports (maybe my PATH is really screwed up > when building from source?)... > > So I tried to install some ports as binaries, but some could not be > found for arm64, so that failed. > > I know that clang and clang++ have been updated successfully and all > the things that I have built outside of MacPorts appear to work, but > only some (very few) of the ports work or even exist now. > > So, what's my next step? Re-install the OS? Yikes. > > Thanks, > Ken Wolcott > > Sigh... >
