-
Notifications
You must be signed in to change notification settings - Fork 131
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
'rnorm' could not be found. Default 'stats' package functions fail to load. #127
Comments
Using dependencywalker, r.dll, rblas.dll or rlapack.dll are the likely modules not found. Why? what has changed. |
In Rengine.Initialize, the line: var status = GetFunction<Rf_initialize_R>()(R_argc, R_argv); changes the content of the PATH env var. Before that call, PATH starts with C:\Program Files\R\R-4.0.2\bin\x64, however after that call it starts with "C:\rtools40\usr\bin". I cannot see what is going on for this to happen. No wonder loading "stats.dll" fails to locate rblas.dll. This appears to have been going on for a while (also with 3.4.4??). Or the behavior is due to an external change. Surely behaviors have changed at some point, otherwise many unit tests would have failed in the past. |
Tried to compile R from source on Windows to diagnose why R changes the PATH env var. See SO post. |
Figured out that the reason why the PATH and R_HOME env var are reset by the R native engine are because I have an %userprofile%\Documents.Renviron that specifies /* Process R_HOME/etc/Renviron.site, then
.Renviron or ~/.Renviron, if it exists.
Only used here in embedded versions */
if(!Rp->NoRenviron) {
process_site_Renviron();
process_user_Renviron();
} |
Resolved with R.NET 1.9.0, at least on Windows |
Trying to release an update for R 4.0.x
Unit tests outputs that the function 'rnorm' could not be found. This is part of the stats package that's always available.
Looking in debug mode, the evaluation results in:
Usually this is a sign that a DLL dependency of stats.dll cannot be loaded (of course, stupid LoadLibrary message fails to say which module could not be found)
The text was updated successfully, but these errors were encountered: