If there is work going on to improve Rtools
1. one of the most annoying aspects of it is that it does not play nice
with builtin Windows commands. In particular, it defines a command
called find which works like UNIX find but it masks Windows find
if you add the Rtools folders to your PATH making
On Tue, Feb 13, 2018 at 7:58 PM, Peter Langfelder
wrote:
> On Tue, Feb 13, 2018 at 2:20 AM, Jeroen Ooms wrote:
>
>> Thanks for your question. Your logs show that 'gcc' is not found. As
>> of R 3.3 you need to set the path to the compiler using the BINPREF
>> variable. This is because we ship two
On Tue, Feb 13, 2018 at 2:20 AM, Jeroen Ooms wrote:
> Thanks for your question. Your logs show that 'gcc' is not found. As
> of R 3.3 you need to set the path to the compiler using the BINPREF
> variable. This is because we ship two separate versions of gcc, one
> targeting win32 and one targetin
On Tue, Feb 13, 2018 at 7:45 AM, Peter Langfelder
wrote:
> Hi all,
>
> I'm trying to set up the Windows Rtools toolset for building packages
> with compiled code. I installed for Windows R-3.4.3 from CRAN and
> installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and
> M:\R\Rtools-3.4
>
> Follow
Thanks for the report - this has been already reported as bug 17376, it
is caused by scripts that build the Windows binaries and by now has been
fixed in R-patched and R-devel snapshot builds. So as a solution that
works now I would recommend using R-patched.
Tomas
On 02/13/2018 08:33 AM, Sø
I can confirm the behaviour that you report.
Usually I put Rtools in c:\programs\Rtools and modify the path
accordingly. Recently (don't recall for how long) I have encountered
the same problems as you have and I have resorted to moving Rtools to
c:\Rtools
I have no idea as how to proceed; perha
