Opened 8 weeks ago
Last modified 8 weeks ago
#70834 closed defect
Error installing UPX on Mac OS X Sequoia (15.0) on MacBook 15 — at Version 1
Reported by: | punkish (punkish) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | UPX |
Description (last modified by 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