Error installing UPX on Mac OS X Sequoia (15.0) on MacBook 15

[punkish (punkish)]

:info:configure ---------------------------------------------
:info:configure CMake 3.9.6, Copyright 2000-2017 Kitware, Inc. and Contributors
:info:configure C compiler on this system is: /usr/bin/clang -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch arm64 -std=gnu11
:info:configure ---------------------------------------------
:info:configure Error when bootstrapping CMake:
:info:configure Cannot find appropriate C++ compiler on this system.
:info:configure Please specify one using environment variable CXX.
:info:configure See cmake_bootstrap.log for compilers attempted.

This is the third program today that has errored out while installing, so I am wondering if I am actually missing something. As far as a C++ compiler is concerned, I do have gcc

gcc --version
Apple clang version 16.0.0 (clang-1600.0.26.3)
Target: arm64-apple-darwin24.0.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

MacPorts installation page says that I need xcode command line tools

Apple's Command Line Developer Tools, in case a port you're installing or one of its dependencies are not available as binaries.

I do have those as is evident below

$ xcode-select --install
xcode-select: note: Command line tools are already installed. Use "Software Update" in System Settings or the softwareupdate command line interface to install updates

Further on, the installation page says

(Optional) Apple's Xcode Developer Tools, when building some ports from source. MacPorts will let you know if this is the case.

So, my question is, is the above error MacPorts way of letting me know that I need the full Xcode Developer Tools? I had not until today and everything I threw at MacPorts worked just fine. But starting today, I am facing these messages. The only difference -- now I have upgraded to Mac OS X Sequoia

[punkish (punkish)]

I downloaded the latest MacPort pkg again, reinstalled it, and ran sudo port -v selfupdate and got the following message

Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.


receiving file list ... done
./

sent 74 bytes  received 98 bytes  114.67 bytes/sec
total size is 35371530  speedup is 205648.43
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
Failed to parse file R/R-pbdMPI/Portfile: can't read "mpi_port": no such variable
Failed to parse file lang/rust-bootstrap/Portfile: rust_build.version (1.77.0) must be newer than rust_build.stage0_versions (1.80.1 1.80.0)

Total number of ports parsed:	2
Ports successfully parsed:	0
Ports failed:			2
Up-to-date ports skipped:	39668


The ports tree has been updated.
All installed ports are up to date.

So, what does "Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option" mean and what do I have to do to correct this?

[punkish (punkish)]

I uninstalled and reinstalled the commandline tools and got a bit more ahead with installing upx before I hit another roadblock with python310 (see below for the error). I think this maybe because sometime ago I upgraded python to 3.12, but upx seems to depend on python310 and tries to install it, but croaks with the following error

$ tail -50 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/main.log
:debug:install removing file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/destroot/+CONTENTS
:debug:install removing file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/destroot/+DESC
:debug:install removing file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/destroot/+COMMENT
:debug:install dropping privileges: euid changed to 502, egid changed to 501.
:debug:activate activate phase started at Fri Sep 20 19:10:16 CEST 2024
:debug:activate elevating privileges for activate: euid changed to 0, egid changed to 0.
:debug:activate Executing org.macports.activate (python310)
:msg:activate --->  Activating python310 @3.10.15_0+lto+optimizations
:error:activate Failed to activate python310: Image error: /Applications/MacPorts/Python 3.10/IDLE.app/Contents/Info.plist already exists and does not belong to a registered port.  Unable to activate port python310. Use 'port -f activate python310' to force the activation.
:error:activate     while executing
:error:activate "throw registry::image-error $msg"
:error:activate     ("foreach" body line 77)
:error:activate     invoked from within
:error:activate "foreach file $imagefiles {
:error:activate                 incr progress_step
:error:activate                 _progress update $progress_step $progress_total_steps
:error:activate                 se..."
:error:activate     invoked from within
:error:activate "registry::write {
:error:activate             foreach file $imagefiles {
:error:activate                 incr progress_step
:error:activate                 _progress update $progress_step $progress_..."
:debug:activate Error code: registry::image-error
:debug:activate Backtrace: Image error: /Applications/MacPorts/Python 3.10/IDLE.app/Contents/Info.plist already exists and does not belong to a registered port.  Unable to activate port python310. Use 'port -f activate python310' to force the activation.
:debug:activate     while executing
:debug:activate "throw registry::image-error $msg"
:debug:activate     ("foreach" body line 77)
:debug:activate     invoked from within
:debug:activate "foreach file $imagefiles {
:debug:activate                 incr progress_step
:debug:activate                 _progress update $progress_step $progress_total_steps
:debug:activate                 se..."
:debug:activate     invoked from within
:debug:activate "registry::write {
:debug:activate             foreach file $imagefiles {
:debug:activate                 incr progress_step
:debug:activate                 _progress update $progress_step $progress_..."
:debug:activate     while executing
:debug:activate "throw [dict get $eOptions -errorcode] [dict get $eOptions -errorinfo]"
:debug:activate     (procedure "_activate_contents" line 256)
:debug:activate     invoked from within
:debug:activate "_activate_contents $requested $rename_list"
:debug:activate     (procedure "portimage::activate" line 65)
:debug:activate     invoked from within
:debug:activate "registry_activate $subport $_inregistry_version $_inregistry_revision $_inregistry_variants $reg_options"
:debug:activate     (procedure "portactivate::activate_main" line 20)
:debug:activate     invoked from within
:debug:activate "$procedure $targetname"
:debug:activate dropping privileges: euid changed to 502, egid changed to 501.
:error:activate See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/main.log for details.

What can I do next?

[ryandesign (Ryan Carsten Schmidt)]

Only you know why "/Applications/MacPorts/Python 3.10/IDLE.app/Contents/Info.plist already exists and does not belong to a registered port." You can remove /Applications/MacPorts/Python 3.10 and then try installing python310 again but if you can't explain why it already existed then you may run into this problem with other ports in the future.

[ryandesign (Ryan Carsten Schmidt)]

Since your original problem was caused by having a faulty configuration of command line tools installed, which is being tracked under #70750, let's close this ticket as a duplicate of that one.

Your new problem about python310 is unrelated and since you've already filed #70837 about that let's continue that there.