BiocManager::install("org.Hs.eg.db")
Bioconductor version 3.8 (BiocManager 1.30.10), R 3.5.2 (2018-12-20)
Installing package(s) 'org.Hs.eg.db'
installing the source package ‘org.Hs.eg.db’
试开URL’https://bioconductor.org/packages/3.8/data/annotation/src/contrib/org.Hs.eg.db_3.7.0.tar.gz'
Content type 'application/x-gzip' length 77962833 bytes (74.4 MB)
downloaded 74.4 MB
* installing *source* package 'org.Hs.eg.db' ...
** R
** inst
** byte-compile and prepare package for lazy loading
Error: package or namespace load failed for 'AnnotationDbi' in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]):
there is no package called 'RSQLite'
Error : package 'AnnotationDbi' could not be loaded
ERROR: lazy loading failed for package 'org.Hs.eg.db'
* removing 'd:/Documents/R/win-library/3.5/org.Hs.eg.db'
In R CMD INSTALL
The downloaded source packages are in
‘C:\Users\Administrator\AppData\Local\Temp\RtmpmObljz\downloaded_packages’
Installation path not writeable, unable to update packages: boot, class,
cluster, codetools, KernSmooth, lattice, MASS, Matrix, mgcv, nlme, nnet,
rpart, spatial, survival
Old packages: 'backports', 'dplyr', 'ellipsis', 'ggforce', 'ggraph', 'glue',
'graphlayouts', 'isoband', 'jsonlite', 'openssl', 'pkgload', 'ps',
'RcppArmadillo', 'rlang', 'tidygraph', 'tidyr', 'tidyselect', 'vctrs'
Update all/some/none? [a/s/n]: n
Warning message:
In install.packages(...) :
installation of package ‘org.Hs.eg.db’ had non-zero exit status
Would you please help me what is the problem for? and how can I solve it?
Thank you very much
Thanks ,Miguel.I removed it.
The problem is solved? - as per Miguel's second point, it looks like you first need to install the
RSQLite
package.Yeah.I 've solved the problem.thanks,Kevin
Generally it is not necessary, and highly unadvisable, to install R or its packages as administrator.
Interesting. I didn't know it was unadvisable, could you explain why is it that way?
That usually helps me when receiving package installation errors.
Administrator accounts can do much more damage (e.g., deleting other user files; access data that might be restricted from a normal user) than a user account; the general principle is to use minimal permissions required for a task.
Usually what happens is that you start with an administrator installation, and then subsequently only an administrator can update or fix (e.g., remove a package) the installation. If instead you'd started with a regular user installation, then the regular user could update or fix the installation.