Install new R language packages

Link: => fronanbika.nnmcloud.ru/d?s=YToyOntzOjc6InJlZmVyZXIiO3M6MzY6Imh0dHA6Ly9iYW5kY2FtcC5jb21fZG93bmxvYWRfcG9zdGVyLyI7czozOiJrZXkiO3M6MjE6Ikluc3RhbGwgcGFja2FnZXMgaW4gciI7fQ==


Package Name, or help Package Name to get the information about the package. The modifier is also used to indicate the script latin, cyrillic for Serbian, iqtelif or language dialect e. For most a 32-bit version is the default, but for some e.

Messages are divided into domains, and translations may be available for some or all messages in a domain. Suitable distributions include Strawberry Perl, and ActivePerl,.

How to Install, Load, and Unload Packages in R

This manual is for R, version 3. Copyright © 2001—2018 R Core Team Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team. If you install packages in r the build to be usable by a group of users, set umask before unpacking so that the files will be readable by the target group e. Keep this setting of umask whilst building and installing. For the two weeks prior to the release of a minor 3. The tarballs are available from. They are built in exactly the same way as distributions of R releases. Note that retrieving the sources by e. To use rsync to install the appropriate sources for the recommended packages, run. These are installed in platform-specific ways, so for the rest of this chapter we consider only building from the sources. Cross-building is not possible: installing R builds a minimal version of R and then runs many R scripts to complete the build. Choose a directory to install the R tree R is not just a binary, but has additional data sets, help files, font metrics etc. This should create directories src, doc, and several more under a top-level directory: change to that top-level directory At this point North American readers should consult. Issue the following commands: make check Failures are not necessarily problems as they might be caused by missing functionality, but you should look carefully at any reported discrepancies. R may indicate inadequate resource limits see. Note that these checks are only run completely if the recommended packages are installed. You could also copy the man page R. If you want to install the complete R tree to, e. Note: you do not need to install R: you can run it from where it was built. install packages in r This has the advantage of always keeping your source tree clean and is particularly recommended install packages in r you work with a version of R from Subversion. It is unlikely to work if the source directory has previously been used for a build. Note: if you already have R installed, check that where you installed R replaces or comes earlier in your path than the previous installation. This is enabled by the configure option --enable-prebuilt-html. It is also possible that system security measures will prevent the server from being started, for example if the loopback interface has been disabled. You will not be able to build any of these unless you have texi2any version 5. Rd and upright quotes, neither of which are contained in the standard LaTeX Computer Modern fonts. We have provided four alternatives: times The default. Using standard PostScript fonts, Times Roman, Helvetica and Courier. This works well both for on-screen viewing and for printing. One disadvantage is that the Usage and Examples sections may come out rather wide: this can be overcome by using in addition either of the options inconsolata on a Unix-alike only if found by configure or beramono, which replace the Courier monospaced font by Inconsolata or Bera Sans mono respectively. You will need a recent version of the appropriate LaTeX package inconsolata or bera installed. This needs LaTeX packages times, helvetic and if used courier installed. These are not often installed as part of a TeX distribution, but can obtained from and mirrors. This install packages in r fonts rather similar to Computer Modern, but is not so good on-screen as times. This is a large installation, obtainable from and its mirrors. These type-1 fonts have poor hinting and so are nowhere near as readable on-screen as the other three options. There are three fonts for which it will need to use bitmapped fonts, tctt0900. Unfortunately, if those files are not available, Acrobat Reader will substitute completely incorrect glyphs so you need to examine the logs carefully. For example, if you prefer to hyperlink the text and not the page number in the table of contents use make install A parallel make can be used but run make before make install. This is known as the R home directory. The prefix of the installation directories can be seen in the status message that is displayed at the end of configure. The installation may need to be done by the owner of prefix, often a root account. More precise control is available at configure time via options: see configure --help for details. Configure options --bindir and --mandir are supported and govern where a copy of the R script and the man page are installed. The configure or make variables rdocdir and rsharedir can be used to install the system-independent doc and share directories to somewhere other than libdir. Note that installing R into a directory whose path contains spaces is not supported, and some aspects such as installing source packages will not work. More precise control is possible. A staged installation is possible, that it is installing R into a temporary directory in order to move the installed tree to its final destination. You can optionally install the run-time tests that are part of make check-all by make uninstall optionally specifying prefix etc in the same way as specified for installation. This will also uninstall any installed manuals. Target uninstall-tests will uninstall any installed tests, as well as removing the directory tests containing the test results. Here name can be anything non-empty, and is used to name subdirectories of lib, etc, include and the package libs subdirectories. When sub-architectures are used the version of Rscript in e. Normally all installed architectures will run on the platform so the architecture of Rscript itself does not matter. If the Linux distribution supports multilib, then parallel builds of R may be installed in the sub-directories lib 32-bit and lib64 64-bit. The build to be run may then be selected using the setarch command. For example, a 32-bit build may be run by setarch i686 R The setarch command is only operational if both 32-bit and 64-bit builds are installed. If there is only one installation of R, then this will always be run regardless of the architecture specified by the setarch command. There can be problems with installing packages on the non-native architecture. It is a good idea to run e. When this mechanism is used, the version of Rscript in e. Normally all installed architectures will run on the platform so the architecture of Rscript does not matter. Almost all of those not listed elsewhere in this manual are either standard autoconf options not relevant to R or intended for specialist uses by the R developers. One that may be useful when working on R itself is the option --disable-byte-compiled-packages, which ensures that the base and recommended packages are not byte-compiled. This will be preferred where there are issues with the system implementation, usually involving install packages in r after 2037 or before 1916. Note that overridden values are not tested. The inferred values can be overridden in file config. Some compilers by default assume a later standard than C++98 whereas the latter has been assumed by some packages. At least for versions 4. Currently the default C++ standard is that of the compiler used: from R 3. This re-runs all the tests relevant to the installed R including for example the code in the package vignettesbut not for example the ones checking the example code in the manuals nor making the standalone Rmath library. This affects both checking the package examples part of make check and package sources part of make check-devel and make check-recommended. Alternatively, the installed R can be run, preferably with --vanilla. It is possible to test the installed packages but not their package-specific install packages in r by testInstalledPackages even if make install-tests was not run. Your file system must allow long file names as is likely except perhaps for some network-mounted systems. Installation is via the installer R-3. Just double-click on the icon and follow the instructions. When installing on a 64-bit version of Windows the options will include 32- or 64-bit versions of R and the default is to install both. You can uninstall R from the Control Panel. Note that you will be asked to choose a language for installation, and install packages in r choice applies to both installation and un-installation but not to running R itself. See the for more details on the binary installer. The standard installer combines 32-bit and 64-bit builds into a single executable which can then be installed into the same location and share all the files except the. This directory can be populated using make rsync-extsoft. A suitable collection of files can also be obtained from or. See and perhaps updates in for details. You should run it first, to obtain a working tar and other necessities. The directory name should not contain spaces. It is also possible to obtain the source code using Subversion; see for details. Look through the file MkRules. Please make sure you install the right version: there is a 32-bit version and a 64-bit version. You may need to compile under a case-honouring file system: we found that a samba-mounted file system which maps all file names to lower case did not work. However, aggressive anti-virus checking such as the on-access scanning of Sophos can slow the build down several-fold. It is not built by default, and needs to be built after make all by make cairodevices. To enable the building of these devices you need to install the static cairographics libraries built by Simon Urbanek at. A suitable distribution can be found via and its unpacked location should be specified in file MkRules. For secure use of e. If a test fails, there will almost always be a. See the section in the Unix-alike section for setting options such as the paper size and the fonts used. By default it is assumed that texinfo is not installed, and the manuals will not be built. The comments in file MkRules. Copy that file to MkRules. The first four targets are the default build if just make or make all is run. Parallel make is not supported and likely to fail. Then after having customized file MkRules, possibly via MkRules. Both methods create an executable with a standard name such as R-3. The defaults for the startup parameters may also be customized. Then the make rinstaller step copies the files that differ between architectures from the 32-bit build as it builds the installer image. This is intended for use by sysadmins doing automated installs, and is not recommended for casual use. Once WiX is installed, set the path to its home directory in MkRules. Then cd installer make msi which will result in a file with a name like R-3. Thanks to David del Campo Dept of Statistics, University of Oxford for suggesting WiX and building a prototype installer. Windows 64-bit is now completely integrated into the R and package build systems: a 64-bit build is selected in file MkRules. Launch either Rgui or Rterm, preferably with --vanilla. These tests can be run from anywhere: they write some of their results in the tests folder of the R home directory as given by R. Click on that, then download the file R-3. Installers for R-patched and R-devel are usually available from. To install, just double-click on the icon of the file you downloaded. This is an Apple Installer package. Note the the installer is clever enough to try to upgrade the last-installed version of the application where you installed it which may not be where you want this time …. For building R from source, see. If you cannot find it there it was possibly installed elsewhere so try searching for it in Spotlight. This is usually referred to as R. You can run command-line R and Rscript from a Terminal so these can be typed as commands like any other Unix-alike: see the next chapter of this manual. It has been reported that running R. Using the X11 device or the X11-based versions of View and edit for data frames and matrices the latter are the default for command-line R but not R. So do the tcltk package and some third-party packages. The un-installation is as simple as removing those folders e. You can use pkgutil --forget if you want the Apple Installer to forget about install packages in r package without deleting its files useful for the R framework when installing multiple R versions in parallelor after you have deleted the files. This can be avoided by using pkgutil --forget see the previous section. A version of R can be run directly from the command-line as e. This is of limited use as R. This may allow you to install a development version of R de-selecting R. Various environment variables can be set to determine where R creates its per-session temporary directory. The path should be an absolute path not containing spaces and it is best to avoid non-alphanumeric characters such as +. A package is loaded from a library by the function library. Changing the set of default packages is normally used to reduce the set for speed when scripting: in particular not using methods will reduce the start-up time by a factor of up to two. But it can also be used to customize R, e. Both sites and users can create others and make use of them or not in an R session. Binary packages are platform-specific and generally need no special tools to install, but see the documentation for your platform for details. Note that you may need to specify implicitly or explicitly the library to which the package is to be installed. This is only an issue if you have more than one library, of course. Alternatively, packages can be downloaded and installed from within R. Unless the library is specified argument lib the first library in the library search path is used: if this is not writable, R will ask the user in an interactive session if the default personal library should be created, and if allowed to will install the packages there. If you want to fetch a package and all those it depends on in any way that are not already installed, use e. Function setRepositories can select amongst those repositories that the R installation is aware of. Naive users sometimes forget that as well as installing a package, they have to use library to make its functionality available. On Windows it looks by default first at the list of binary versions of packages available for your version of R and downloads the latest versions if any. Windows binary packages for R are distributed as a single binary containing either or both architectures 32- and 64-bit. A few of the binary packages need other software to be installed on your system: see for example. Packages using Gtk+, and those that depend on them need the bin directory of a bundled distribution of Gtk2 from or in the path: it should work to have both 32- and install packages in r Gtk+ bin directories in the path on a 64-bit version of R. No additional tools are needed if the package does not contain compiled code, and install. If you have only a source package that is known to work with current R and just want a binary Windows build of it, you could make use of the building service offered at. It will report success if the installation of the architecture of the running R succeeded, whether or not the other architecture was successfully installed. The exceptions are packages with a non-empty configure. This install packages in r only be applied to a tarball, and will only succeed if both installs succeed. However, such a package can be installed from the sources on Windows without install packages in r additional tools. Packages with compiled code may need to have paths to the compilers set explicitly, and there is provision to make use of a system-wide library of installed external software. On R builds using binary packages, the default is type both: this looks first at the list of binary packages available for your version of R and installs the latest versions if any. Note that most binary packages including compiled code are tied to a particular series e. Installing source packages which do not contain compiled code should work with no additional tools. Package and those which depend on it need a Java runtime installed and several packages need X11 installed, including those using Tk. A few of the binary packages need other software to be installed on your system. At the time of writing these setting assumed that the C, Fortran and C++ compilers were on the path, using gfortran 6. If installing packages from source using them it is usually easiest to install a statically-linked up-to-date copy of the Open Install packages in r package from its sources or from. Note that this mechanism can also be used when it necessary to change the optimization level for a particular package. There is also provision for a site-wide Makevars. Fortunately such packages are unusual. These are commonly used on Windows but can in principle be used on other platforms. install packages in r When a source package is installed by a build of R which supports multiple sub-architectures, the normal installation process installs the packages for all sub-architectures. Windows where there is a non-empty configure. In install packages in r cases only the current architecture is installed. Not all contributed packages work correctly when byte-compiled. For most packages especially those which make extensive use of compiled code the speed-up is small. Unless a package is used frequently the time spent in byte-compilation can outweigh the time saved in execution: also byte-compilation can add substantially to the installed size of the package. Standard library locations will be covered by the cache, and well-designed software will add its locations as for example openmpi does on Fedora. The danger with any of the methods which involve setting environment variables is of inadvertently masking a system library. It downloads the list of available packages and their current versions, compares it with those installed and offers to fetch and install any that have later versions on the repositories. An alternative interface to keeping packages up-to-date is provided by the command packageStatuswhich returns an object with information on all installed packages and packages available at multiple repositories. The print and summary methods give an overview of installed and available packages, the upgrade method offers to fetch and install the latest versions of outdated packages. Other forms of compression can be used, e. If you have a mis-configured server that does not report correctly non-existent files you may need these files. To add your repository to the list offered by setRepositoriessee the help install packages in r for that function. Incomplete repositories are better specified via a contriburl argument than via being set as a repository. If multiple sub-architectures fail only because they need different settings, e. So on Windows to install, check and package for distribution a source package from a tarball which has been tested on another platform one might use. These are interpreted according to the current locale, a sufficiently complicated topic to merit a separate section. The other aspect of the internationalization is support for the translation of messages. This is enabled in almost all builds of R. Aspects of the locale are accessed by the R functions Sys. There is quite wide agreement on schemes, but not on the details of install packages in r implementation. Sometimes the combination of language and territory is used to specify the encoding, for example to distinguish between traditional and simplified Chinese. install packages in r The modifier is also used to indicate the script latin, cyrillic for Serbian, iqtelif or language dialect e. R is principally concerned install packages in r the first for translations and third. See man locale and locale -a for more details. It offers only one encoding per language. For example, chinese is Traditional Chinese and not Simplified Chinese as used in most of the Chinese-speaking world. See for how users can set their locales. The last three are normally used to set the locale and so should not be needed, but the first is only used to select the language for messages. It is usually possible to change the language once R is running via not Windows Sys. Messages are divided into domains, and translations may be available for some or all messages in a domain. R makes use of the following domains. Dividing up the messages in this way allows R to be extensible: as packages are loaded, their message translation catalogues can be loaded too. R can be built without support for translations, but it is enabled by default. R-level and C-level domains are subtly different, for example in the way strings are canonicalized before being passed for translation. However, if a specific translation catalogue exists but does not contain a translation, the less specific catalogues are consulted. install packages in r Translations in the right language but the wrong charset are made use of by on-the-fly re-encoding. See for how to prepare and install translation catalogues. For most a 32-bit version is the default, but for some e. The principal difference is in the size of the pointers. The limits for 64-bit processes are much larger e. R allocates memory for large objects as needed, and removes any unused ones at garbage collection. When the sizes of objects become an appreciable fraction of the address limit, fragmentation of the address space becomes an issue and there may be no hole available that is the size requested. This can cause more frequent garbage collection or the inability to allocate large objects. As a guide, this will become an issue for 32-bit builds with objects more than 10% of the size of the address space around 300Mb or when the total size of objects in use is around one third around 1Gb. This can often be worked around: configure selects suitable defines if this is possible. We have also largely worked around that limit on 32-bit Windows. This means that R objects take more space and usually more time to manipulate. So 64-bit builds of R will, install packages in r other things being equal, run slower than 32-bit builds. On Sparc Solaris the difference was 15-20%. So, for speed you may want to use a 32-bit build especially on a laptopbut to handle large datasets and perhaps large files a 64-bit build. You can often build both and install them in the same place: See. This is done for the Windows binary distributions. These can be compiled into a standalone library for linking to other applications. Note that they are not a separate library when R is built, and the standalone version differs in several ways. A little care is needed to use the random-number routines. Note that you will probably not be able to run it unless you add the directory containing libRmath. It is possible to link to Rmath. For versions of gcc prior to 5. A suitably comprehensive iconv function is essential. Some C99 functions are required and checked for at configuration. Installations of zlib version 1. See also the comments for Solaris. Information on libcurl is found from the curl-config script: if that is missing or needs to be overridden there are macros to do so described in file config. A tar program is needed to unpack the sources and packages including the recommended packages. You will not be able to build most of the manuals unless you have texi2any version 5. Further, the versions of texi2dvi and install packages in r. If you want to build from the R Subversion repository then texi2any is highly recommended as it is used to create files which are in the tarball but not stored in the Subversion repository. Note that package hyperref currently requires packages kvoptions, ltxcmds and refcount. Pango needs to be at least version 1. These tests will fail if pkg-config is not installed, and are likely to fail if cairo was built statically unusual. Most systems with Gtk+ 2. On platforms which have it available, the msttcorefonts package provides TrueType versions of Monotype fonts such as Arial and Times New Roman. These share metrics with Arial, Times New Roman and Courier New, and contain fonts rather similar to the first two. See the R help on X11 on selecting such fonts. The bitmapped graphics devices jpegpng and tiff need the appropriate headers and libraries installed: jpeg version 6b or later, or libjpeg-turbo or libpng version 1. They also need support for either X11 or cairo see above. Should support for these devices not be required or broken system libraries need to be avoided there are configure options --without-libpng, --without-jpeglib and --without-libtiff. Recent versions allow several other libraries to be linked into libtiff such as lzma, jbig and jpeg12, and these may need also to be present. The latest 2016 sources are in the git repository atbut at the time of writing the resulting build will not pass its checks. Use of the X11 clipboard selection requires the Xmu headers and libraries. These are normally part of an X11 installation e. The bitmap and dev2bitmap devices and function embedFonts use ghostscript. This check can be suppressed by configure option --disable-java. Renvironwhich suffices to run already-installed Java-using packages. Other packages need full Fortran 90 or later support. For source files with extension. This is found when R is configured and is often the same as F77: note that it is detected by the name of the command without a test that it can actually compile Fortran 90 code. The correct incantation for these is often found via --with-blas with no value on the appropriate platforms. This is checked in the test suite. The reference implementations are thread-safe but external ones may not be even single-threaded ones : this install packages in r lead to hard-to-track-down incorrect results or segfaults. Unfortunately it is built by default as a static library that on some platforms may not be able to be used with shared objects such as are used in R packages. For the Fedora libraries the compile-time flag specifies 4 threads. This has both advantages and disadvantages. Note that rebuilding or symlinking libRblas. This can only be done if --with-blas has been used. However, the likely performance gains are thought to be small and may be negative. Other potential problems are incomplete versions of the libraries, seen several times in Linux distributions over the years. Reporting problems where it is used unnecessarily will simply irritate the R helpers. For example, this has meant that on Sun Sparc using the Oracle compilers the flag -dalign is needed if sunperf is to be used. You will want to use --disable-R-profiling if you are building a profiled executable of R e. Flag --enable-R-shlib causes the make process to build R as a dynamic shared library, typically called libR. This can only be done if all the code including system libraries can be compiled into a dynamic library, and there may be a performance penalty. So you probably only want this if you will be using an application which embeds R. Note that C code in packages installed on an R system linked with --enable-R-shlib is linked against the dynamic library and so such packages cannot be used from an R system built in the default way. For maximally effective use of valgrind, R should be compiled with valgrind instrumentation. Level 0 is the default and does not add anything. The system headers for valgrind can be requested by option --with-system-valgrind-headers: they will be used if present on Linux they may be in a separate package such as valgrind-devel. Note though that there is no guarantee that the code in R will be compatible with very old or future valgrind headers. If you need to re-configure R with different options you may need to run make clean or even make distclean before doing so. The configure script has other generic install packages in r added by autoconf and which are not supported for R: in particular building for one architecture on a different host is not possible. There is also a general autoconf mechanism for config. These variables are precious, implying that install packages in r do not have to be exported to the environment, are kept in the cache even if not specified on the command line, checked for consistency between two configure runs provided that caching is usedand are kept during automatic reconfiguration as if having been passed as command line arguments, even if no cache is used. See the variable output section of configure --help for a list of all these variables. If you find you need to alter configure variables, it is worth noting that some settings may be cached in the file config. Note that caching is turned off by default: use the command line option --config-cache or -C to enable caching. This is used both when configuring R to set the default, and when running R to override the default. In this case, use a different compiler or a front-end shell script which does the re-ordering. These flags can also be used to build a faster-running version of R. The default is to search for f95, fort, xlf95, ifort, ifc, efc, pgf95 lf95, gfortran, ftn, g95, f90, xlf90, pghpf, pgf90, epcf90, g77, f77, xlf, frt, pgf77, cf77, fort77, fl32, af77 in that orderand use whichever is found first; if none is found, R cannot be compiled. This is checked during the configuration process. Since R install packages in r a shared library has about 6200 symbols, if in doubt use the larger version. This requires other tools to be installed, discussed in the rest of this section. File configure is created from configure. There is a formal version requirement on autoconf of 2. It is known that earlier versions of bison generate code which reads and in some cases writes outside array bounds: bison 2. The ultimate sources for package compiler are in its noweb directory. Some Linux distributions include this command in package noweb. It can also be installed from the sources at. These notes are based on tests run on one or two systems in each case with particular sets of compilers and support libraries. Success in building R depends on the proper installation and functioning of support software; your results may differ if you have other versions of compilers and support libraries. C macros to select particular platforms can be tricky to track down there is a fair amount of misinformation on the Web. The Wiki currently at can be helpful. As its name implies, it displays on a local or remote X server, and relies on the services provided by the X server. When X11 was designed, most displays were around 75dpi, whereas today they are of the order of 100dpi or more. If you find that X11 is reporting missing font sizes, especially larger ones, it is likely that you are not using scalable fonts and have not installed the 100dpi versions of the X11 fonts. More complicated problems can occur in non-Western-European locales, so if you are using one, the first thing to check is that things work in the C locale. X11 works by being asked for a font specification and coming up with its idea of a close match. In such locales fontsets are used, made up of fonts encoded in other encodings. If not, you may have to get hold of a suitable locale entry for X11. On some systems scalable fonts are available covering a wide range of glyphs. These are generally not part of the default install, and the X server may need to be configured to use them. As from g++ 6 the default C++ standard is C++14. It may also be necessary to set the pkg-config path, e. The current out-of-the-box default for clang++ is to use the C++ runtime from the installed g++. These are desirable when checking packages, to ensure as far as possible that features from later C++ standards are not used unintentionally. It currently produces few diagnostics even with -Wall -pedantic. So it may be necessary to disable the latter by configuring R using --disable-openmp. Others have reported success with versions 10. Bjørn-Helge Mevik reported success with version 2015. R can be built for 10. If you have installed Xcode, this provides the command-line tools. An X sub-system is required unless configuring using --without-x: see. This option needs an Objective-C compiler which can compile the source code of quartz. Use --without-aqua if you want a standard Unix-alike build: apart from disabling quartz and the ability to use the build with R. Various compilers can be used. There are installers for Fortran compilers for El Capitan and Sierra at and. An Apple package for 6. Other recent distributions of clang are often available from : for example at the time of writing of 6. Pre-compiled versions of many of the are available from. You will most likely want at least jpeg and tiff. The pkg-config utility is not provided by Apple and used for the installation from source of many packages: it will also be used if present when configuring the X11 and bitmap devices. You can also install directly a recent Java from Oracle currently from. We recommend you install a version with long-term support, e. Binary distributions of R are built against a specific version e. It is only needed if you want install packages in r build R for use with the R. This option configures R to be built and installed as a framework called R. The default installation path for R. We will only consider 12. There have been few reports on Solaris 11, with no known extra issues. Solaris was last tested on Sparc machines in June 2017. The Solaris versions of several of the tools needed to build R e. Solaris 10 ships install packages in r bzlib version 1. At least when compiling with Oracle compilers, Solaris uses far more stack space than other platforms. The support for the C99 long double type on Sparc hardware uses quad-precision arithmetic, and this is usually slow because it is done by software emulation. On such systems the configure option --disable-long-double can be used for faster but less accurate computations. Using configure option --with-internal-tzcode is recommended, and required if you find time-zone abbreviations being given odd values as has been seen on 64-bit builds without it. The Oracle compilers provide several implementations of the C++98 standard which select both the set of headers and a C++ runtime library. It will also be necessary to point pkg-config at the 64-bit directories, e. This can be ascertained from gcc -v. One of -m32 or -m64 will be the default and could be omitted, but it is not easy to find out which. All tools needed and libraries downloaded from these repositories e. It is strongly recommended to install Bash and use it as the configure shell, e. This mandates the use of plus and minus infinity and NaN not a number as well as specific details of rounding. On a new platform you must find out the magic recipe and add some code to make it work. This can often be done via the file config. Beware of using high levels of optimization, at least initially. Shared Objects: There seems to be very little agreement across platforms on what needs to be done to build shared objects. This typically works, but you may have to manually override the results. Scanning the manual entries for cc and ld usually reveals the correct incantation. Once you know the recipe you can modify the file config. It seems that gcc 3. If you do manage to get R running on a new platform please let us know about it so we can modify the configuration procedures to include that platform. We have had a fair amount of practice at porting R to new platforms. See for the current locations and other updates to these instructions. install packages in r Most Windows users will not need to build add-on packages from source; see for details. We have found that the build process for R is quite sensitive to the choice of tools: please follow our instructions exactly, even to the choice of particular install packages in r of the tools. The build process for add-on packages is somewhat more forgiving, but we recommend using the exact toolset at first, and only substituting other tools once you are familiar with the process. This appendix contains a lot of prescriptive comments. They are here as a result of bitter experience. Please do not report problems to the R install packages in r lists unless you have followed all the prescriptions. You will need the following items to build R and packages. See the subsections below for detailed descriptions. For installing simple source packages containing data or R source but no compiled code, none of these are needed. The ordering of the other directories is less important, but if in doubt, use the order above. It is also possible to use the TeX Live distribution from. Please read about how to make fullrefman. If you choose to install these yourself, you will need suitable versions of at least basename, cat, cmp, comm, cp, cut, date, diff, du, echo, expr, gzip, ls, make, makeinfo, mkdir, mv, rm, rsync, sed, sh, sort, tar, texindex, touch and uniq; we use those from the Cygwin distribution or compiled from the sources. To avoid frustration, please use our tool set, and make sure it is at the front of your path including before the Windows system directories. This toolchain does not use multilib: separate front-ends are used for 32-bit and 64-bit compilation. To select a 32-bit or 64-bit build of R, set the options in MkRules. Some external software libraries will need to be re-compiled under the new toolchain: especially those providing a C++ interface. Users developing packages with need to ensure that they use a version built with exactly the same toolchain as their package: the recommendation is to build from its sources yourself. Windows binaries of qpdf are available from. Set the path to the qpdf installation in file MkRules. There is a version of the file command that identifies the type of files, and is used by Rcmd check if available. Most aspects will work with paths containing spaces, but external software used by R, e. Instructions on how to install the latest version are at. This will be needed if more than one sub-architecture is to be installed. This includes for clang and the Intel and Oracle compilers. Currently this is a valid option for g++ 5 and later and 2016 versions of the Intel and Solaris compilers. This is true for earlier versions of g++ such as 4. For when features were supported, see. Suitable distributions include Strawberry Perl, and ActivePerl. The framework for R 3. More precisely, of the Apple package of the same name: this means that installing a package for 3. If a proxy needs to be set, see. Look at the source of tools:::. Note that capitalization and version may differ from the Open Source project. Bessel, beta and gamma functions including copying MkRules. However, it is possible to break the default behaviour of glibc by re-specifying the gconv modules to be loaded. Some versions including that from texinfo 5. This is the default as from glibc 2. We believe that versions 3. For example, glibc: other C libraries such as musl have been used but are not routinely tested. It will be necessary to install later versions of software such as libcurl. In the unlikely event that the version reported does not start with 1. Oracle Solaris Studio prior to 2016, and previously Sun Studio. In particular, header cmath in C++11 mode includes math. For example, the Cygwin version of make 3.

This can often be worked around: configure selects suitable defines if this is possible. For example, if you are installing , the installation routine will try to update a bunch of centrally installed packages. So that job is done. There is quite wide agreement on schemes, but not on the details of their implementation. Aspects of the locale are accessed by the R functions Sys. Since R as a shared library has about 6200 symbols, if in doubt use the larger version. Sometimes the combination of language and territory is used to specify the encoding, for example to distinguish between traditional and simplified Chinese. Note that this mechanism can also be used when it necessary to change the optimization level for a particular package. More precise control is possible. There are over 3500 as of Feb 2012 of them? Unfortunately, if those files are not available, Acrobat Reader will substitute completely incorrect glyphs so you need to examine the logs carefully. This toolchain does not use multilib: separate front-ends are used for 32-bit and 64-bit compilation.