This can be corrected by explicitly setting build_arch arm64 in nf, or by using a native terminal emulator. 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. MacPorts defaults to building for the architecture that it is running as. 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
#Darktable m1 mac install#
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. Symptoms that your system requires manual installation: console message about missing SDK ( Warning: The macOS 11.x SDK does not appear to be installed. 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. 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
You also have to agree to the license by running sudo xcodebuild -license. sudo xcode-select -s /Applications/Xcode.app/Contents/Developer), and that you have the command line tools installed ( xcode-select -install). MacPorts must be re-installed in a version configured for macOS 11 Big Sur.Įnsure you have Xcode 12.2 or greater installed and selected (e.g.
0 kommentar(er)
