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.
Mac OS/X universal tarball with llvm-gcc 4.0 and all other LLVM tools This is most useful if you want a no-fuss drop-in replacement for Apple GCC. To install this, sudo to root, then untar in /. This installs tools in /usr/local/bin, which work on either ppc and intel macs. In addition, llvm-gcc supports the -arch option for Apple-style cross. Clang Static Analyzer. The Clang Static Analyzer is a source code analysis tool that finds bugs in C, C, and Objective-C programs. Currently it can be run either from the command line or if you use macOS then within Xcode.When invoked from the command line, it is.
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 4.0.3 'Bunny-Wunnies Freak Out' released on 2020/10/10
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
openssl sha1 R-4.0.3.pkg
in the Terminal application to print the SHA1 checksum for the R-4.0.3.pkg image. On Mac OS X 10.7 and later you can also validate the signature using
pkgutil --check-signature R-4.0.3.pkg
Latest release:
| R-4.0.3.pkg (notarized and signed) SHA1-hash: 8402f586aef1fdb12c6e34c73b286f87318fb1be (ca. 85MB) | R 4.0.3 binary for macOS 10.13 (High Sierra) and higher, signed and notarized package. Contains R 4.0.3 framework, R.app GUI 1.73 in 64-bit for Intel Macs, Tcl/Tk 8.6.6 X11 libraries and Texinfo 6.7. 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. 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 Xcode 10.1 and GNU Fortran 8.2. If you wish to compile R packages from sources, you will need to download and GNU Fortran 8.2 - see the tools directory. |
| NEWS (for Mac GUI) | News features and changes in the R.app Mac GUI |
| Mac-GUI-1.73.tar.gz SHA1-hash: 7f4b1d050757ce78545bdeb9d178a69d13046aa1 | Sources for the R.app GUI 1.73 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.6.3.nn.pkg (signed) 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. |
| 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). |
| base | Binaries of R builds for macOS 10.13 or higher (High Sierra) |
| contrib | Binaries of package builds for macOS 10.13 or higher (High Sierra) |
| 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/10/10, by Simon Urbanek
The Clang Static Analyzer is a source code analysis tool that finds bugs inC, C++, and Objective-C programs. Currently it can be run either from the command line or if you use macOS then within Xcode. Wheninvoked from the command line, it is intended to be run in tandem with a buildof a codebase. The analyzer is 100% open source and is part of the Clang project. Like the rest of Clang, theanalyzer is implemented as a C++ library that can be used by other tools andapplications. DownloadMac OS X
Other PlatformsFor other platforms, please follow the instructions for building the analyzer from source code. | Viewing static analyzer results in a web browser |
What is Static Analysis?
The term 'static analysis' is conflated, but here we use it to meana collection of algorithms and techniques used to analyze source code in orderto automatically find bugs. The idea is similar in spirit to compiler warnings(which can be useful for finding coding errors) but to take that idea a stepfurther and find bugs that are traditionally found using run-time debuggingtechniques such as testing.
Static analysis bug-finding tools have evolved over the last several decadesfrom basic syntactic checkers to those that find deep bugs by reasoning aboutthe semantics of code. The goal of the Clang Static Analyzer is to provide aindustrial-quality static analysis framework for analyzing C, C++, andObjective-C programs that is freely available, extensible, and has a high quality of implementation.
Part of Clang and LLVM
As its name implies, the Clang Static Analyzer is built on top of Clang and LLVM.Strictly speaking, the analyzer is part of Clang, as Clang consists of a set ofreusable C++ libraries for building powerful source-level tools. The staticanalysis engine used by the Clang Static Analyzer is a Clang library, and hasthe capability to be reused in different contexts and by different clients.
Important Points to Consider
While we believe that the static analyzer is already very useful for findingbugs, we ask you to bear in mind a few points when using it.
Download Clang Format
Work-in-Progress
The analyzer is a continuous work-in-progress. There are many plannedenhancements to improve both the precision and scope of its analysis algorithmsas well as the kinds of bugs it will find. While there are fundamentallimitations to what static analysis can do, we have a long way to go beforehitting that wall.
Slower than Compilation
Operationally, using static analysis toautomatically find deep program bugs is about trading CPU time for the hardeningof code. Because of the deep analysis performed by state-of-the-art staticanalysis tools, static analysis can be much slower than compilation.
While the Clang Static Analyzer is being designed to be as fast andlight-weight as possible, please do not expect it to be as fast as compiling aprogram (even with optimizations enabled). Some of the algorithms needed to findbugs require in the worst case exponential time.
The Clang Static Analyzer runs in a reasonable amount of time by bothbounding the amount of checking work it will do as well as using cleveralgorithms to reduce the amount of work it must do to find bugs.
False Positives
Static analysis is not perfect. It can falsely flag bugs in a program wherethe code behaves correctly. Because some code checks require more analysisprecision than others, the frequency of false positives can vary widely betweendifferent checks. Our long-term goal is to have the analyzer have a low falsepositive rate for most code on all checks.
Download Clang Format For Windows
Please help us in this endeavor by reporting falsepositives. False positives cannot be addressed unless we know aboutthem.
Clang Format Mac
More Checks
Update Clang On Mac
Static analysis is not magic; a static analyzer can only find bugs that ithas been specifically engineered to find. If there are specific kinds of bugsyou would like the Clang Static Analyzer to find, please feel free tofile feature requests or contribute your ownpatches.