On 24 January 2018 at 07:55, William Dunlap wrote:
| On Linux you can trace all the getenv calls with ltrace. It only
| works on ELF files, not sh scripts:
|
| % R CMD ltrace -e getenv `R RHOME`/bin/*/R
| libR.so->getenv("R_HOME")
|= "/home/R/R-3.4.3/lib64/R"
| libR.so->getenv("R
On Linux you can trace all the getenv calls with ltrace. It only
works on ELF files, not sh scripts:
% R CMD ltrace -e getenv `R RHOME`/bin/*/R
libR.so->getenv("R_HOME")
= "/home/R/R-3.4.3/lib64/R"
libR.so->getenv("R_TRANSLATIONS")
= nil
libR.so->getenv("R_PLATFORM")
On 24 January 2018 at 07:03, luke-tier...@uiowa.edu wrote:
| If you are picking up an R 3.4.x that is trying to load a package
| built by R-devel you should also see a warning that the package was
| built under R version 3.5.0
Yes, I am of course very aware of the issue.
But we had to separate o
On Wed, 24 Jan 2018, Uwe Ligges wrote:
On 24.01.2018 12:00, Martin Maechler wrote:
Uwe Ligges
on Wed, 24 Jan 2018 11:23:50 +0100 writes:
> On 24.01.2018 03:20, Dirk Eddelbuettel wrote:
>>
>> I am going in circles here and have lost my way. I used to have
means to
On 24 January 2018 at 12:00, Martin Maechler wrote:
| > Uwe Ligges
| > I guess you actually pick up anotehr version of R.
| > Carefully check what is on your PATH and perhaps some Renviron files
| > that may be around?
I did, a million times, hence the frustration.
| Yes exact
On 24.01.2018 12:00, Martin Maechler wrote:
Uwe Ligges
on Wed, 24 Jan 2018 11:23:50 +0100 writes:
> On 24.01.2018 03:20, Dirk Eddelbuettel wrote:
>>
>> I am going in circles here and have lost my way. I used to have means to
>> build R-devel (still do) and use it for
> Uwe Ligges
> on Wed, 24 Jan 2018 11:23:50 +0100 writes:
> On 24.01.2018 03:20, Dirk Eddelbuettel wrote:
>>
>> I am going in circles here and have lost my way. I used to have means to
>> build R-devel (still do) and use it for local testing (no longer do).
>>
On 24.01.2018 03:20, Dirk Eddelbuettel wrote:
I am going in circles here and have lost my way. I used to have means to
build R-devel (still do) and use it for local testing (no longer do).
- Fresh build of R-devel
- One entry in .libPaths()
- I can install Rcpp, it ends up in that .libP
