The pak installer has some workarounds and will definitely have a more informative error message if this occurs. This issue is fundamental to the way Windows is designed, so there are limited things we can do to address it. This issue is compounded by the fact that install.packages() does not fail in these cases, it only issues a warning, so users do not always even realize something has gone wrong until they try to load the package. This restriction means that if you have an R package loaded and try to install a new version of that package, the DLL will be locked.īecause the DLL is locked the old version will not be removed and the new version cannot be copied, so users can end up with a package with new R code and an old DLL, which will break the next time they try to load the package.Īlso if you have multiple versions of R running at the same time this restriction still applies, so if you forgot you had a package loaded in one session and try to update to the latest version in another process your installation will be broken. This applies to all open files, but crucially in R’s case to the DLL files used by an R package with compiled code. Ultimately most of these issues are caused by DLL locking.ĭLLs (Dynamic-link libaries) are what R packages use to link compiled code to the R executable so the compiled code can be run by R.Īny file on Windows cannot be deleted if another process has a handle to it. Windows users report substantially increased numbers of package installation issues compared to other OSs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |