Because my response is a little long and summarizes original thread is
at bottom.
Okay, I tried to implement your test (and the package is installed). My
discovery is that it was RTerm and not
RTools giving me a problem.
Summary: RTerm starts fine if installed on C: even if there is a space
Best regards,
Georgi Boshnakov
-Original Message-
Date: Sat, 11 Mar 2017 11:17:15 -0600
From: Robert Baer
To: "'r-devel@r-project.org'"
Subject: [Rd] Possible issue with R-tools on Windows
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed
This is
regards,
Georgi Boshnakov
-Original Message-
Date: Sat, 11 Mar 2017 11:17:15 -0600
From: Robert Baer
To: "'r-devel@r-project.org'"
Subject: [Rd] Possible issue with R-tools on Windows
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed
This is a
Hmmm, you may know winbuilder: It has R not installed oin drive C: and
works well. Even with R installed on a network share I can easily
install packages.
using R-devel binary in, e.g. for 64 bit: in d:/RCompile/recent/R/bin/x64
working directory: d:/library-devel
specified library: c:/tmp
This is a bit of a cross-post but I've encountered what appears to be a
parsing error with RTools on Windows in a couple of different contexts
on Widows when R is installed on a secondary drive to avoid using
precious space on my c:/ solid state drive.
This type of apparent parsing error has h
