-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with install_cmdstan()
under Windows 10, R 4.4.0, RTools 4.4
#962
Comments
That's a very odd one. What output do you get from: Sys.getenv("PATH")
Sys.getenv("R_RTOOLS44_PATH") |
Also, is this a local computer & installation or a remote cluster/server? |
|
This is a local computer and installation. It's the desktop computer in my office. |
Is there any antivirus software installed aside from the standard Windows defender? |
Only Windows Defender |
Hmm very strange, are you able to install R packages from source? Like: install.packages("jsonlite", type="source") |
I'm getting the same error and can install other packages from source just fine. |
Concerning! Given that the error is concerning dir.create(file.path(tempdir(), "test1"))
dir.exists(file.path(tempdir(), "test1"))
system2("C:/rtools44/usr/bin/mkdir.exe", file.path(tempdir(),"test2"))
dir.exists(file.path(tempdir(), "test2")) |
Ok, I figured it out (in my case at least). There was a 'problem with the toolchain' even though I had installed rtools 4.4. This problem was nicely detected and fixed by cmdstanr, but only after I tried to update cmdstan. |
I also had trouble getting everything in working order after upgrade from R 4.3.x to R 4.4.0 on Windows 10. The following steps worked for me:
|
Describe the bug
I get a fatal error when running
install_cmdstan()
under Windows 10, R 4.4.0, RTools 4.4To Reproduce
Run
install_cmdstan()
Expected behavior
Successful installation of cmdstan.
Operating system
Windows 10
CmdStanR version number
0.7.1, freshly installed from GitHub, SHA = 21888fa
Additional context
Followed by a stack trace.
Session Info
The text was updated successfully, but these errors were encountered: