R Installation and Administration

1 R Installation and AdministrationVersion (2023-04-21)R Core TeamThis manual is for R, version (2023-04-21).Copyrightc 2001 2023 R Core TeamPermission is granted to make and distribute verbatim copies of this manual providedthe copyright notice and this permission notice are preserved on all is granted to copy and distribute modified versions of this manual underthe conditions for verbatim copying, provided that the entire resulting derived workis distributed under the terms of a permission notice identical to this is granted to copy and distribute translations of this manual into an-other language, under the above conditions for modified versions.

2 Except that thispermission notice may be stated in a translation approved by the R Core of Contents1 Obtaining Getting and unpacking the Getting patched and development Using Subversion and Installing R under Simple Help Making the Other Debugging OpenMP C++ C Link-Time LTO with LTO with LTO for package Testing an Installing R under Building from The Windows Checking the Testing an Installing R under Running R under Uninstalling under Multiple Running Add-on Default Managing Installing Customizing package Multiple External Updating Removing Setting up a package Checking installed source Internationalization and Locales under Locales under Locales under Localization of Choosing between 32- and 64-bit The standalone Rmath A Essential and useful otherprograms under a Essential programs and Useful libraries and Java Other compiled Linear OpenBLAS and Intel Shared

3 B Configuration on a Configuration Internationalization Configuration Setting paper Setting the Compilation Making Setting the Using Using Compile and load Maintainer C Platform X11 Intel Fortran Cairo Other C/C++ Other Tcl/Tk headers and Building Building binary Building for Intel on arm64 .. New and variable variable Obtaining RSources, binaries and documentation for R can be obtained viaCRAN, the ComprehensiveR Archive Network whose current members are listed Getting and unpacking the sourcesThe simplest way is to download the most , and unpack it withtar -xf systems that have a suitable1tarinstalled.

4 On other systems you need to have thegzipprogram installed, when you can usegzip -dc | tar -xf -The pathname of the directory into which the sources are unpacked should not contain spaces,as mostmakeprograms (and specificallyGNUmake) do not expect you want the build to be usable by a group of users, setumaskbefore unpacking so thatthe files will be readable by the target group ( ,umask 022to be usable by all users). Keepthis setting ofumaskwhilst building and you use a fairly recentGNUversion oftarand do this as a root account (which onWindows includes accounts with administrator privileges) you may see many warnings aboutchanging ownership.

5 In which case you can usetar --no-same-owner -xf perhaps also include the option--no-same-permissions. (These options can also be setin theTAR_OPTIONS environment variable: if more than one option is included they should beseparated by spaces.) Getting patched and development versionsA patched version of the current release, r-patched , and the current development version, r-devel , are available as daily tarballs and via access to the R Subversion repository. (Forthe two weeks prior to the release of a minor ( ) version, r-patched tarballs may refer tobeta/release candidates of the upcoming release, the patched version of the current release beingavailable via Subversion.)

6 The tarballs are available (or ) and unpack as described inthe previous section. They are built in exactly the same way as distributions of R Using Subversion and rsyncSources are also available , the R Subversion repository. Ifyou have a Subversion client ( ), you can check out andupdate the current r-devel the current r-patched from (wherexandyare the major and minor number of the current released version of R). , usesvn checkout check out r-devel into directorypath(which will be created if necessary).The alpha, beta and RC versions of an are available from in the four-week period prior tothe or later, or that from the libarchive (as used on macOS) or Heirloom Toolchest 1: Obtaining R2 Note that https: is required2, and that the SSL certificate for the Subversion server of theR project should be recognized as from a trusted that retrieving the sources by -rorsvn exportfrom that URL will not work(and will give a error early in themakeprocess).

7 The Subversion information is needed to Subversion repository does not contain the current sources for the recommended pack-ages, which can be obtained byrsyncor downloaded fromCRAN. To usersyncto install theappropriate sources for the recommended packages, thetop-level directory of the R downloading manually fromCRAN, do ensure that you have the correct versions ofthe recommended packages: if the number in the fileVERSIONis you need todownload the contents of , wherediris for r-devel r-patched, respectively, todirectorysrc/library/Recommendedin the sources you have unpacked.

8 After downloadingmanually you need to executetools/link-recommendedfrom the top level of the sources tomake the requisite links insrc/library/Recommended. A suitable incantation from the toplevel of the R sources usingwgetmight be (for the correct value ofdir)wget -r -l1 --no-parent -A\*.gz -nd -P src/library/Recommended \ some Subversion clients http: may appear to work, but requires continual Installing R under Unix-alikesR will configure and build under most common Unix and Unix-alike platforms including cpu-*-linux-gnu for the alpha , arm64 , hppa , ix86 , m68k , mips , mipsel #, ppc64 , s390x , sparc64 , and x86_64 CPUs, x86_64-apple-darwin and aarch64-apple-darwin 1as well as perhaps (it is tested less frequently on these platforms)

9 I386-sun-solaris , i386-*-freebsd , x86_64-*-freebsd , i386-*-netbsd , x86_64-*-openbsd and powerpc-ibm-aix6* In addition, binary distributions are available for some common Linux distributions (see theFAQfor current details) and for macOS. These are installed in platform-specific ways, so for therest of this chapter we consider only building from the is not possible: installing R builds a minimal version of R and then runs manyR scripts to complete the Simple compilationFirst review the essential and useful tools and libraries inAppendix A [Essential and usefulother programs under a Unix-alike], page 39, and install those you want or need.

10 Ensure thateither the environment variableTMPDIRis either unset (and/tmpexists and can be written inand scripts can be executed from) or points to the absolute path to a valid temporary directory(one from which execution of scripts is allowed) which does not contain a directory to install the R tree (R is not just a binary, but has additional datasets, help files, font metrics etc). Let us call this placeRHOME. Untar the source code. Thisshould create directoriessrc,doc, and several more under a top-level directory: change to thattop-level directory (At this point North American readers should consultSection [Settingpaper size], page 52.)