| | 1 | = macOS Monterey Problems = |
| | 2 | |
| | 3 | == General Issues == |
| | 4 | |
| | 5 | First of all, please read [wiki:Migration]. |
| | 6 | |
| | 7 | == Updating MacPorts Base == |
| | 8 | |
| | 9 | MacPorts must be [https://www.macports.org/install.php re-installed] in a version configured for macOS 12 Monterey. |
| | 10 | |
| | 11 | Ensure you have Xcode 13.1 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`). You also have to agree to the license by running `sudo xcodebuild -license`. |
| | 12 | |
| | 13 | 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` |
| | 14 | |
| | 15 | == Rosetta 2 and build_arch == |
| | 16 | |
| | 17 | MacPorts defaults to building for the architecture that it is running as. If you have a universal MacPorts installation on an Apple Silicon Mac, and you run it from a terminal emulator that is not a native arm64 binary, MacPorts will end up being run as x86_64, and will build ports accordingly, which can be unexpected. This can be corrected by explicitly setting `build_arch arm64` in macports.conf, or by using a native terminal emulator. |
| | 18 | |
| | 19 | == Tickets for Broken Ports == |
| | 20 | |
| | 21 | [[TicketQuery(component=ports&status!=closed&keywords~=monterey,or,component=ports&status!=closed&keywords~=12.0)]] |
| | 22 | [[TicketQuery(component=ports&status!=closed&keywords!~=monterey,and,keywords!~=12.0&summary~=Monterey,or,summary=~[^0-9]12\.0[^0-9])]] |
