All software on this page is strictly experimental and subject to acceptance of the supplied R license agreement and the disclaimer at the end of the page.
In addition to this nightly generated page, visit the Building R page for the most recent tips.
| Build | OS | Date | Status | Download |
|---|---|---|---|---|
| R-2.6-branch R 2.6.2 Patched (2008-03-24) | tiger | Apr 1 02:44 | i386: OK (log) ppc: OK (log) universal: OK | R-2.6-branch-tiger-universal.tar.gz (23Mb) R-2.6-branch-45011.dmg (25Mb, installer incl. GUI) |
| R-2.7-branch R 2.7.0 Patched (2008-05-14) | tiger | May 15 03:08 | i386: OK (log) ppc: OK (log) universal: OK | R-2.7-branch-tiger-universal.tar.gz (23Mb) R-2.7-branch-45690.dmg (25Mb, installer incl. GUI) |
| R-devel R 2.8.0 Under development (unstable) (2008-05-14) | tiger | May 15 03:08 | i386: OK (log) ppc: OK (log) universal: OK | R-devel-tiger-universal.tar.gz (23Mb) R-devel-45690.dmg (25Mb, installer incl. GUI) |
| R-2.6-branch R 2.6.2 Patched (2008-03-24) | leopard | Apr 1 02:44 | i386: OK (log) ppc: OK (log) x86_64: OK (log) ppc64: OK (log) universal: OK | R-2.6-branch-leopard-universal.tar.gz (25Mb) |
| R-2.7-branch R 2.7.0 Patched (2008-05-12) | leopard | May 15 01:58 | i386: make FAILED
(log) ppc: make FAILED (log) x86_64: make FAILED (log) ppc64: OK (log) universal: FAILED: Missing build result for R-2.7-branch-leopard-x86_64 Missing build result for R-2.7-branch-leopard-ppc Missing build result for R-2.7-branch-leopard-i386 | |
| R-devel R 2.8.0 Under development (unstable) (2008-05-13) | leopard | May 15 01:58 | i386: make FAILED
(log) ppc: make FAILED (log) x86_64: make FAILED (log) ppc64: OK (log) universal: FAILED: Missing build result for R-devel-leopard-x86_64 Missing build result for R-devel-leopard-ppc Missing build result for R-devel-leopard-i386 | |
Important note: Leopard builds above are strictly experimental and not supported by CRAN. Although CRAN packages may accidentally be compatible, they exist only for 32-bit, so for 64-bit R you must use install.packages(...,type='source') and have all necessary development tools. The only build intentionally compatible with CRAN packages is the R-2.6-branch.
Requirements: Mac OS X 10.4.4 or higher for Tiger builds and Mac OS X 10.5 or higher for Leopard builds. For additional tools necessary for compiling packages, see below.
The installer image (*.dmg) is packaged exactly the same way as the CRAN release of R (including the GUI) and it will update your R version (unless you delete the last receipt - see instructions during installation). Alternatively you can use the tar-ball (*.tar.gz) which must be unpacked in the root (e.g. tar fvxz R*.tar.gz -C /), but doesn't contain the GUI (see below for a separate download).
For experimental/beta binary builds of packages use http://r.research.att.com/ repository.
The build results for CRAN can be found at the CRAN check summary page. For Bioconductor packages see http://r.research.att.com/results/. Package maintainers, please check this page after you release a new package or version.
| Version | Build | Download |
|---|---|---|
| Mac OS X GUI rev. 5041 for R 2.6.x | Deployment | R-GUI-5041-2.6-Deployment.dmg |
| Mac OS X GUI rev. 5130 for R 2.7.x | Deployment | R-GUI-5130-2.7-Deployment.dmg |
| Mac OS X GUI rev. 5130 for R 2.8.x | Deployment | R-GUI-5130-2.8-Deployment.dmg |
| Mac OS X GUI rev. 5041 for R 2.6.x | Deployment | R-GUI-5041-2.6-Deployment.dmg |
| Mac OS X GUI rev. 5130 for R 2.7.x | Deployment | R-GUI-5130-2.7-Deployment.dmg |
| Mac OS X GUI rev. 5130 for R 2.8.x | Deployment | R-GUI-5130-2.8-Deployment.dmg |
To install, open the image and drag the R icon to your Applications folder. Alternatively the GUI can be run directly off that image without copying if you just want to test it.
Starting with R 2.5.0 CRAN binaries use Apple's 10.4u SDK allowing universal builds on both PowerPC and Intel Macs. Building universal R is done by compliling two R binaries and setting r_arch parameter to ppc and i386 respectively, along with the proper compiler flags. Those two builds can then be installed into the same framework location, R install process merges them correspondingly.
To build an universal package that contains a configure script, it is necessary to run R CMD twice. Assuming you have a source package foo_0.1.tar.gz, this is how you install it universally: