= macOS Big Sur Problems =

== General Issues ==

First of all, please read [wiki:Migration].

== Updating MacPorts Base ==

MacPorts must be [https://www.macports.org/install.php re-installed] in a version configured for macOS 11 Big Sur.

Ensure you have Xcode 12.2 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`. 

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`

== Install macOS SDK 11 manually in case of problems == 

Some users who upgraded from earlier versions of macOS reported, that `xcode-select --install` didn't gave proper results (didn't install neither Xcode, nor the SDK required) and first the installation of Xcode from AppStore and then the installation of `Command-line tools for Xcode 12.2` was required from Apple Developer site, as described here: https://www.macports.org/install.php . 

Symptoms that your system requires manual installation: console message about missing SDK (`Warning: The macOS 11.x SDK does not appear to be installed. Ports may not build correctly. Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.`) or a message about C compiler being unable to create executables in build logs. 

If `xcode-select --install` shows that the command-line tools are already installed, but `ls /Library/Developer/CommandLineTools/SDKs/` did not list the desired version, you need to download the installer from Apple developer center manually

[https://developer.apple.com/download/all/?q=command%20line%20tools developer.apple.com]

== Rosetta 2 and build_arch ==

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 is often unexpected. This can be corrected by explicitly setting `build_arch arm64` in macports.conf, or by using a native terminal emulator.

== Rebuilding from source ==

Some port problems can be worked around by instructing MacPorts to build the port on your machine from source, rather than using the prebuilt version. For example, this might be the case if the version of the macOS SDK used on our build machine is different from the one on your machine. Instead of running `sudo port install`, try running `sudo port -s install`. If that fixes the problem, please report it to us so that it can be fixed properly.

== Tickets for Broken Ports ==

[[TicketQuery(component=ports&status!=closed&keywords~=bigsur,or,component=ports&status!=closed&keywords~=11.0)]]
[[TicketQuery(component=ports&status!=closed&keywords!~=bigsur,and,keywords!~=11.0&summary~=Big Sur,or,summary=~[^0-9]11\.0[^0-9])]]