Thanks for all your input. I am now aware that the R environment
running configure will have set R_HOME. I had sometimes been running
./configure without R_HOME set, leading to my problem (since in this
case, the configure snippet does assume 'R'). I'll stick to the
official build routine from now
On 26 September 2015 at 22:29, peter dalgaard wrote:
|
| > On 26 Sep 2015, at 17:43 , Dirk Eddelbuettel wrote:
| >
| > R_HOME is set to the result of the command R RHOME if and only it is unset.
| >
| > And it usually is unset.
|
| Did you actually mean that, Dirk?
Yes. But I didn't make my
> On 26 Sep 2015, at 17:43 , Dirk Eddelbuettel wrote:
>
> R_HOME is set to the result of the command R RHOME if and only it is unset.
>
> And it usually is unset.
Did you actually mean that, Dirk? I would expect that R_HOME would be set by
"myR CMD whatever" before it got to the configure sc
Not sure I understand what you're doing and in what context, but if
you're trying to query R for where it lives, the following may help.
Note that executables or where they live do *not* follow solely from
R.home() - there's more to it.
## Windows
$ Rscript -e "R.home()"
[1] "C:/PROGRA~1/R/R-devel
On 26 September 2015 at 12:32, Jack Wasey wrote:
| Dirk, thanks for detailed reply. I may not have explained myself well enough.
I
| think the problem is that the recommended configure command assumes 'R', not
If and only if R_HOME is unset. But witness:
edd@max:~$ R --slave -e 'Sys.getenv("R
Dirk, thanks for detailed reply. I may not have explained myself well
enough. I think the problem is that the recommended configure command
assumes 'R', not the actually running RD, Rdevel etc, when inferring
R_HOME. I can indeed set R_HOME, but I want my configure script to be able
to figure out w
On 26 September 2015 at 10:27, Jack Wasey wrote:
| Having just read section 1.2 in Writing R extensions, a fragment of a
| configure script is offered in order to determine the correct compiler
| options. It starts by setting R_HOME with:
|
| : ${R_HOME=`R RHOME`}
|
|
| `R` is called, even if,
Hello,
Having just read section 1.2 in Writing R extensions, a fragment of a
configure script is offered in order to determine the correct compiler
options. It starts by setting R_HOME with:
: ${R_HOME=`R RHOME`}
`R` is called, even if, as in my case, `Rdevel` is the command used to
invoke pack
