Changes between Initial Version and Version 1 of GoldenGateProblems

Timestamp:

Sep 14, 2026, 10:24:32 PM (4 weeks ago)

Author:

jmroot (Joshua Root)

Comment:

--

GoldenGateProblems

@@ +1 @@
+= macOS Golden Gate Problems =
+
+== General Issues ==
+
+First of all, please read [wiki:Migration].
+
+Check the status of Golden Gate builders [https://build.macports.org/builders here] if you prefer to install prebuilt binaries. It can take several weeks after a new macOS release before builders finish building ports.
+
+== Updating MacPorts Base ==
+
+MacPorts must be [https://www.macports.org/install.php installed] in a version configured for macOS 27 Golden Gate. If you update from an older OS version, you need to run `port migrate` to reinstall MacPorts base and installed ports that are not OS-independent (see link above).
+
+Ensure you have Xcode 27.0 or greater installed and selected (e.g. `sudo xcode-select -s /Applications/Xcode.app/Contents/Developer`), and that you have the command line tools installed (`xcode-select --install`). (See below for a potential problem when upgrading from older CLT versions.) You also have to agree to the license by running `sudo xcodebuild -license`. 
+
+There have been reports that the `-license` option might not be sufficient alone, and following command might be required to agree to the license: `sudo xcodebuild -runFirstLaunch`
+
+== Compiling C++ fails ==
+
+The installer for the Command Line Tools for Xcode 16 and later may not delete a directory that was installed by some older versions of the CLTs, which unfortunately causes clang++ to look in the wrong place for C++ headers. The majority of ports that contain C++ code will fail to build as a result.
+
+The fix is to delete the stray directory if it exists: `sudo rm -rf /Library/Developer/CommandLineTools/usr/include/c++`
+
+Then clean the ports that failed to build, and try again.
+
+Ticket: #70750
+
+== Trace mode not working ==
+
+Building ports in trace mode (i.e. with the `-t` option) will fail on Apple Silicon systems running Golden Gate. This appears to be due to new security features in Ventura+. This issue is being followed in Ticket: #66358
+
+== Rosetta 2 ==
+
+A number of MacPorts portfiles and MacPorts base assume that arm64 Macs will have Rosetta 2 installed; you will likely run into issues if you have not installed it. Note that Rosetta 2 is not installed by default, or when running x86_64 binaries from the command line — you must open an application that has only x86_64 code in it to get the prompt to install Rosetta 2, or run {{{softwareupdate --install-rosetta}}} in a terminal window.
+
+== Metal toolchain is no longer bundled in Xcode ==
+Since Xcode 26 the Metal toolchain is a separate Xcode component and no longer automatically included out-of-the-box.
+Ports that require the Metal toolchain to build (at least `qt6-qtwebengine`, `openjdk17`, `openjdk21`, `openjdk25` and `openjdk26`) will thus fail to build if the Metal toolchain is not set up correctly for the MacPorts user.
+
+Port maintainers that maintain ports that require the Metal toolchain to build are encouraged to adopt the new `metal` PortGroup for these ports.
+The `metal` PortGroup checks if the Metal toolchain is set up correctly, attempts to correct the setup, and provides an actionable error message when the Metal toolchain setup cannot be fixed automatically.
+
+MacPorts users need to ensure that MacPorts has been updated to at least 2.11.6, and will need to install the Metal toolchain component:
+
+{{{
+sudo port selfupdate
+xcodebuild -downloadComponent MetalToolchain
+}}}
+
+Then verify that the Metal toolchain component has status `installed`:
+
+{{{
+❯ xcodebuild -showComponent MetalToolchain
+(...)
+Status: installed
+(...)
+}}}
+
+Also verify that the MacPorts user is able to execute it to report the Metal toolchain version:
+
+{{{
+sudo --user=macports xcrun metal --version
+}}}
+
+If the command above returns an error, try killing the xcrun cache for the MacPorts user (it will be recreated), and test again:
+
+{{{
+sudo --user=macports xcrun --kill-cache
+sudo --user=macports xcrun metal --version
+}}}
+
+Finally, it may be [ticket:73262 necessary] to reboot to really clear the {{{xcrun}}} cache.
+
+Shoutout to Mark Mentovai for all his detective work! See #73008 for more details.
+
+== Tickets for Broken Ports ==
+
+[[TicketQuery(component=ports&status!=closed&keywords~=goldengate,or,component=ports&status!=closed&keywords~=27.0)]]
+[[TicketQuery(component=ports&status!=closed&keywords!~= goldengate,and,keywords!~=27.0&summary~=Golden%20Gate,or,summary=~[^0-9]27\.0[^0-9])]]