Trouble installing GMT 5.1.0 on a Mac. Added by Yves about 6 years ago. Hello, A few months ago, I installed GMT 5.0.1b on my iMac with the application bundle without any problem. I have tried to install the new GMT 5.1.0 and got (almost) nowhere. I have modified my.bashprofile to include the new path to GMT binary executables (/Applications. Installing NetCDF library in your computer. On Linux and Mac OS X machines typically you can install NetCDF from the main software repositories (with 'yum' or similar package manage on Linux or MacPorts on Mac). You can try it, but we don't recommend this approach. The problem is that for a library to be compatible with your Fortran compiler it.
This directory contains binaries for a base distribution and packages to run on Mac OS X (release 10.6 and above). Mac OS 8.6 to 9.2 (and Mac OS X 10.1) are no longer supported but you can find the last supported release of R for these systems (which is R 1.7.1) here. Releases for old Mac OS X systems (through Mac OS X 10.5) and PowerPC Macs can be found in the old directory.
Note: CRAN does not have Mac OS X systems and cannot check these binaries for viruses.Although we take precautions when assembling binaries, please use the normal precautions with downloaded executables.
Package binaries for R versions older than 3.2.0 are only available from the CRAN archive so users of such versions should adjust the CRAN mirror setting (https://cran-archive.r-project.org) accordingly.
R 3.6.3 'Holding the Windsock' released on 2020/02/29
Important: since R 3.4.0 release we are now providing binaries for OS X 10.11 (El Capitan) and higher using non-Apple toolkit to provide support for OpenMP and C++17 standard features. To compile packages you may have to download tools from the tools directory and read the corresponding note below.
Please check the MD5 checksum of the downloaded image to ensure that it has not been tampered with or corrupted during the mirroring process. For example type
md5 R-3.6.3.pkg
in the Terminal application to print the MD5 checksum for the R-3.6.3.pkg image. On Mac OS X 10.7 and later you can also validate the signature using
pkgutil --check-signature R-3.6.3.pkg
md5 R-3.6.3.pkg
in the Terminal application to print the MD5 checksum for the R-3.6.3.pkg image. On Mac OS X 10.7 and later you can also validate the signature using
pkgutil --check-signature R-3.6.3.pkg
Latest release:
R-3.6.3.pkg (notarized, for Catalina) SHA1-hash: 2677aaf9da03e101f9e651c80dbec25461479f56 (ca. 77MB) R-3.6.3.nn.pkg (regular) SHA1-hash: c462c9b1f9b45d778f05b8d9aa25a9123b3557c4 (ca. 77MB) | R 3.6.3 binary for OS X 10.11 (El Capitan) and higher, signed package. Contains R 3.6.3 framework, R.app GUI 1.70 in 64-bit for Intel Macs, Tcl/Tk 8.6.6 X11 libraries and Texinfo 5.2. The latter two components are optional and can be ommitted when choosing 'custom install', they are only needed if you want to use the tcltk R package or build package documentation from sources. macOS Catalina users must use notarized version which enforces hardened run-time. All others can use regular version which uses the same runtime as previous R releases. R 3.6.2 was the last version that can be run on Catalina with regular runtime. Note: the use of X11 (including tcltk) requires XQuartz to be installed since it is no longer part of OS X. Always re-install XQuartz when upgrading your macOS to a new major version. Important: this release uses Clang 7.0.0 and GNU Fortran 6.1, neither of which is supplied by Apple. If you wish to compile R packages from sources, you will need to download and install those tools - see the tools directory. |
NEWS (for Mac GUI) | News features and changes in the R.app Mac GUI |
Mac-GUI-1.70.tar.gz MD5-hash: b1ef5f285524640680a22965bb8800f8 | Sources for the R.app GUI 1.70 for Mac OS X. This file is only needed if you want to join the development of the GUI, it is not intended for regular users. Read the INSTALL file for further instructions. |
Note: Previous R versions for El Capitan can be found in the el-capitan/base directory.Binaries for legacy OS X systems: | |
R-3.3.3.pkg MD5-hash: 893ba010f303e666e19f86e4800f1fbf SHA1-hash: 5ae71b000b15805f95f38c08c45972d51ce3d027 (ca. 71MB) | R 3.3.3 binary for Mac OS X 10.9 (Mavericks) and higher, signed package. Contains R 3.3.3 framework, R.app GUI 1.69 in 64-bit for Intel Macs, Tcl/Tk 8.6.0 X11 libraries and Texinfo 5.2. The latter two components are optional and can be ommitted when choosing 'custom install', it is only needed if you want to use the tcltk R package or build package documentation from sources. Note: the use of X11 (including tcltk) requires XQuartz to be installed since it is no longer part of OS X. Always re-install XQuartz when upgrading your OS X to a new major version. |
R-3.2.1-snowleopard.pkg MD5-hash: 58fe9d01314d9cb75ff80ccfb914fd65 SHA1-hash: be6e91db12bac22a324f0cb51c7efa9063ece0d0 (ca. 68MB) | R 3.2.1 legacy binary for Mac OS X 10.6 (Snow Leopard) - 10.8 (Mountain Lion), signed package. Contains R 3.2.1 framework, R.app GUI 1.66 in 64-bit for Intel Macs. This package contains the R framework, 64-bit GUI (R.app), Tcl/Tk 8.6.0 X11 libraries and Texinfop 5.2. GNU Fortran is NOT included (needed if you want to compile packages from sources that contain FORTRAN code) please see the tools directory. NOTE: the binary support for OS X before Mavericks is being phased out, we do not expect further releases! |
Subdirectories:
tools | Additional tools necessary for building R for Mac OS X: Universal GNU Fortran compiler for Mac OS X (see R for Mac tools page for details). |
el-capitan | Binaries of package builds for OS X 10.11 or higher (El Capitan build) |
mavericks | Binaries of package builds for Mac OS X 10.9 or higher (Mavericks build) |
old | Previously released R versions for Mac OS X |
You may also want to read the R FAQ and R for Mac OS X FAQ. For discussion of Mac-related topics and reporting Mac-specific bugs, please use the R-SIG-Mac mailing list.
Information, tools and most recent daily builds of the R GUI, R-patched and R-devel can be found at http://mac.R-project.org/. Please visit that page especially during beta stages to help us test the Mac OS X binaries before final release!
Package maintainers should visit CRAN check summary page to see whether their package is compatible with the current build of R for Mac OS X.
Binary libraries for dependencies not present here are available from http://mac.R-project.org/libs and corresponding sources at http://mac.R-project.org/src.
Last modified: 2020/03/07, by Simon Urbanek
-->PowerShell supports macOS 10.12 and higher.All packages are available on our GitHub releases page.After the package is installed, run
pwsh
from a terminal.Note
PowerShell 7 is an in-place upgrade that removes PowerShell Core 6.x.
The
/usr/local/microsoft/powershell/6
folder is replaced by /usr/local/microsoft/powershell/7
.If you need to run PowerShell 6 side-by-side with PowerShell 7, reinstall PowerShell 6 using thebinary archive method.
About Brew
Homebrew is the preferred package manager for macOS. If the
brew
command is not found, youneed to install Homebrew following their instructions. Otherwise you may install PowerShellvia Direct Download or fromBinary Archives.Installation of latest stable release via Homebrew on macOS 10.12 or higher
See About Brew for information about Brew.
Now, you can install PowerShell:
Finally, verify that your install is working properly:
When new versions of PowerShell are released,update Homebrew's formulae and upgrade PowerShell:
Note
The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgradeand refresh the values shown in
$PSVersionTable
.Installation of latest preview release via Homebrew on macOS 10.12 or higher
See About Brew for information about Brew.
After you've installed Homebrew, you can install PowerShell.First, install the Cask-Versions package that lets you install alternative versions of cask packages:
Now, you can install PowerShell:
Finally, verify that your install is working properly:
When new versions of PowerShell are released,update Homebrew's formulae and upgrade PowerShell: Adventure capitalist download for mac.
Note
The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgrade.and refresh the values shown in
$PSVersionTable
.Installation via Direct Download
Download the PKG package
powershell-6.2.0-osx-x64.pkg
from the releases page onto your macOS machine.You can double-click the file and follow the prompts,or install it from the terminal:
Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIM operations.
Install as a .NET Global tool
If you already have the .NET Core SDK installed, it's easy to install PowerShellas a .NET Global tool.
Binary Archives
PowerShell binary
tar.gz
archives are provided for the macOS platformto enable advanced deployment scenarios.Installing binary archives on macOS
Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIM operations.
Installing dependencies
Install XCode command-line tools
Install OpenSSL
OpenSSL is needed for PowerShell remoting and CIM operations. You can install via MacPorts or Brew.
Install OpenSSL via Brew
See About Brew for information about Brew.
To install OpenSSL, run
brew install openssl
.Install OpenSSL via MacPorts
- Install the XCode command line tools.
- Install MacPorts.If you need instructions, refer to theinstallation guide.
- Update MacPorts by running
sudo port selfupdate
. - Upgrade MacPorts packages by running
sudo port upgrade outdated
. - Install OpenSSL by running
sudo port install openssl
. - Link the libraries to make them available to PowerShell:
Uninstalling PowerShell
If you installed PowerShell with Homebrew, use the following command to uninstall:
If you installed PowerShell via direct download, PowerShell must be removed manually:
To remove the additional PowerShell paths, refer to the paths section in this documentand remove the paths using
sudo rm
.Note
This is not necessary if you installed with Homebrew.
Paths
$PSHOME
is/usr/local/microsoft/powershell/6.2.0/
- User profiles will be read from
~/.config/powershell/profile.ps1
- Default profiles will be read from
$PSHOME/profile.ps1
- User modules will be read from
~/.local/share/powershell/Modules
- Shared modules will be read from
/usr/local/share/powershell/Modules
- Default modules will be read from
$PSHOME/Modules
- PSReadline history will be recorded to
~/.local/share/powershell/PSReadLine/ConsoleHost_history.txt
The profiles respect PowerShell's per-host configuration.So the default host-specific profile exists at
Microsoft.PowerShell_profile.ps1
in the same locations.PowerShell respects the XDG Base Directory Specification on macOS.
Because macOS is a derivation of BSD, the prefix
/usr/local
is used instead of /opt
.So, $PSHOME
is /usr/local/microsoft/powershell/6.2.0/
, and the symbolic link is placed at /usr/local/bin/pwsh
.