18 May 2013 08:54
R CMD config for R >= 3.0.1
Berwin A Turlach <Berwin.Turlach <at> gmail.com>
2013-05-18 06:54:34 GMT
2013-05-18 06:54:34 GMT
Dear all,
When installing the usual packages that I use, after installing R
3.0.1, I noticed that the installation of some packages that query R about
its configuration did not succeed. The problem is exemplified by:
berwin <at> bossiaea:~$ R-3.0.1 CMD config CC
/opt/R/R-3.0.1/lib/R/bin/config: 222: .: Can't open /opt/R/R-3.0.1/lib/R/etc/Renviron
Prior to R 3.0.1 such commands worked fine:
berwin <at> bossiaea:~$ R-3.0.0 CMD config CC
gcc -std=gnu99
I noticed now that my installations of the development and
patched version of R have the same problem (since I usually do not install
packages in those versions that query the configuration, I hadn't
noticed the issue earlier).
The problem seems to be line 222 of `R RHOME`/bin/config (when R is R
3.0.1) which reads:
. ${R_HOME}/etc/Renviron
The file ${R_HOME}/etc/Renviron does not necessarily exists if one has
opted for 32/64-bit builds and installed both as sub-architectures,
which I have. In my installation ${R_HOME}/etc/32/Renviron and
${R_HOME}/etc/64/Renviron exist, but no ${R_HOME}/etc/Renviron.
Is it necessary for R >= 3.0.1 to have one build as
(Continue reading)
RSS Feed