search for: rtools43_home

...resolves Make and GCC and try to run tools:::.shlib_internal(c('-n', 'hello.c')) or tools:::.shlib_internal('hello.c'), does it do something useful? (I'm still debugging from first principles. Duncan Murdoch is likely right that adding the environment variables, either RTOOLS43_HOME=c:/rtools43 or adjusting PATH as described above, could help.) -- Best regards, Ivan

...everything only using R without RStudio to avoid this extra layer of potential dependencies (but it also does not work if I try within RStudio anyway). I am also not sure how this could be related to the paths: on my personal laptop (on which everything works fine), the only paths related to R are RTOOLS43_HOME (C:/rtools43) and RTOOLS42_HOME (C:/rtools42). The same paths that are currently set on my work laptop. It was not working neither when I tried to add other paths related to R on my work laptop.

...nternal('hello.c'), does it do something useful? I think I tried the commands in the right R session. Here are all the output related to the environment variables for R as well as Sys.which(): ``` > Sys.getenv("RTOOLS42_HOME") [1] "C:/rtools42" > Sys.getenv("RTOOLS43_HOME") [1] "C:/rtools43" > Sys.getenv("R_USER") [1] "C:\\Users\\Christophe Bousquet\\Documents" > Sys.getenv("R_RTOOLS43_PATH") [1] "C:/rtools43/x86_64-w64-mingw32.static.posix/bin;C:/rtools43/usr/bin" > Sys.getenv("R_LIBS_USER")...

TL:DR there are at least three maybe four ways to address this depending on what you plan to do. I usually adjust PATH to add Rtools using .Rprofile. But if you do that then if you want to use the command line to invoke R then you need to set the PATH separately when you start the shell. For this reason some people like to set it in the User Environment Variables control panel... but some Rtools