I suspect that the number of people supporting MacPorts itself (not just
specific ports) is quite small; and they're doing it in their "spare" time, at
that.
What is typically involved in updating MacPorts itself (and any ports that have
to be updated with it before others can be checked), and
Dear MacPorts:
I write to propose a policy change: a MacPorts release for a new macOS major
version should be publicly available by the time Apple publishes the final
Release Candidate version of macOS.
Rationale: MacPorts is an annual problem for me. I’m a Mac developer who needs
to install
Maxim, thanks. Yours is the third report of compile or link problems
related to Command Line Tools 15.0, released only two days ago, that I have
seen. I do not know what to make of that error message. I have not heard
of "xcodebuild -version" failing when Xcode was actually installed. Other
Dear Dave et al.,
I’m unable to run the ‘xcodebuild —version’. It complains:
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer
directory '/Library/Developer/CommandLineTools' is a command line tools instance
The version of Xcode reported by the ‘About Xcode’ graphical
Dear all,
I can compile and link the code with Clang C++ compiler from the MacPorts
collection:
clang version 15.0.7
Target: x86_64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /opt/local/libexec/llvm-15/bin
To complement my previous email: my target system is macOS 13.5.2 (22G91) and
Dear all,
How are you? I hope all is well with you. I need help please. I’m no longer
able to compile and link a C++ code on my Mac. I use the latest GNU C++
compiler available via MacPorts:
g++ (MacPorts gcc12 12.3.0_0+stdlib_flag) 12.3.0
Please find below the output of the make tool:
g++
