![]() Users of Xcode 3 or earlier can install them by ensuring that the appropriate Or they can be installed from within Xcode back to version 4. Older versions are found at the Apple Developer site, With Xcode 4 and later, users need to accept the Xcode EULA by either launching Xcode or running: xcodebuild -licenseĪpple's Command Line Developer Tools, which can be installed on recent OS versions by running this command in the Terminal: xcode-select -install OS is highly recommended, except for Snow Leopard where the last free version, 3.2.6, is recommended. Using the latest available version that will run on your Site, on your Mac operating system installation CDs/DVD, or in the Mac App Store. Snow Leopard, or 3.1 or later for Leopard), found at the Apple Developer Please note that in order to install and run MacPorts on macOS, your system must have installations of the followingĪpple's Xcode Developer Tools (version 13.1 or later for Monterey,Ĩ.0 or later for Sierra, 7.0 or later for El Capitan,Ħ.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, The public key to verify the detached GPG signatures can be found under the attachments section on jmr's wiki page. MacPorts installed and wish to upgrade to a newer release.Ĭhecksums for our packaged downloads are contained in the corresponding checksums file. The selfupdate target of the port(1) command, for users who already have.Git clone of the unpackaged sources, if you wish to follow MacPorts development.Tar.gz one for manual compilation, if you intend to customize your installation In source form as either a tar.bz2 package or a. ![]() Procedure that most users should follow after meeting the requirements listed MacPorts version 2.7.2 is available in various formats for download and installation (note, if you are upgrading to a new major release of macOS, see the migration info page): Install MacPorts for your version of the Mac operating system:.Agree to Xcode license in Terminal: sudo xcodebuild -license.Install Xcode and the Xcode Command Line Tools.Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. ( about development of a package for Root using CMake)īug_revision_view_page.php?rev_id=1203#r1203įor reference, the full thread where we previously discussed this is here: Per-language platform information variable, perhaps called The hard-coded flag needs to be replaced with a lookup of a new Would be used in combination with CMAKE_OSX_ARCHITECTURES would It was added to CMake way back when universal binary support wasįirst added to OS X under the assumption that all compilers that a=blob f=Source/cmLocalGenerator.cxx hb=v2.8.10.2#l1826 The flag "-arch x86_64" shouldn't be there. Misc/minicern/CMakeFiles/minicern.dir/flags.makeĮnds up containing the following variables (among others):Ĭ_FLAGS = -m64 -pipe -W -Wall -fsigned-char -fno-common -O2 -g-arch x86_64 -fPIC -Iįortran_FLAGS = -m64 -std=legacy -arch x86_64 -fPIC -I In that particular project the generated file DCMAKE_INSTALL_PREFIX=/path/to/install \ I could probably try to prevent DCMAKE_OSX_ARCHITECTURES from being passed to cmake (via some tricks in MacPorts or by modifying MacPorts sources), but I still believe that passing "-arch x86_64" to Fortran_FLAGS is a bug in CMake.Ĭompiled Root () or any minimal project which needs Fortran with The g95 compiler ignores "-arch " flag, but GCC's gfortran 4.x throws an error and breaks compilation. That flag CMAKE_OSX_ARCHITECTURES is added automatically to all projects in MacPorts (third-party package manager for Mac OS X) even when cross-compiling or compilation of fat binaries (like i386 x86_64) is not needed, so no project that needs Fortran and CMake can be compiled (luckily there are not many such projects, but it's still a showstopper to switch to CMake). 0014252: Unsupported "-arch x86_64" mysteriously ends up in Fortran_FLAGSĪn unsupported compiler flag "-arch x86_64" mysteriously sneaks into Fortran_FLAGS when
0 Comments
Leave a Reply. |