Closed cmfield closed 1 year ago
You can 'see' that Rsamtools installs on the Bioconductor linux builder (under the current Bioc release using R-4.2 & Bioc devel using R-devel.
Yes, and I actually managed to install it on another machine. Is it possible that an older chipset (~5yrs) could have a problem?
My guess would be the /nfs mount. You say 'lazy load'; can you elaborate? Is it at this stage here...
* installing *source* package ‘Rsamtools’ ...
** using staged installation
** libs
...
** R
** inst
** byte-compile and prepare package for lazy loading
<illegal instruction here ???>
...
My guess would be the /nfs mount. You say 'lazy load'; can you elaborate? Is it at this stage here...
* installing *source* package ‘Rsamtools’ ... ** using staged installation ** libs ... ** R ** inst ** byte-compile and prepare package for lazy loading <illegal instruction here ???> ...
Yes, exactly at that point.
I see this very similar report but for a different package suggesting perhaps that the cpu node being used for the installation doesn't have a full installation of Rsamtools dependencies? Maybe the immediate dependencies are satisfied, but underlying dependencies are not... You could try to install all dependencies explicitly
> db = available.packages(repos = BiocManager::repositories())
> pkgs = tools::package_dependencies("Rsamtools", db, recursive=TRUE)[[1]]
> BiocManager::install(c("Rsamtools", pkgs))
or do a sanity check
setdiff(pkgs, rownames(installed.packages())) ## should be the empty set
Thanks, I'll give it a go.
Is this issue still active?
Well, I still could not get to install on the first machine and I suspect it's the chipset not supporting a recent core library because it's otherwise identical to the newer machine on which it did install - nothing I can put my finger on, but maybe a cautionary tale for others. Feel free to close the issue.
Describe the bug When the lazy loading stage is reached it crashes:
To Reproduce BiocManager::install("Rsamtools")
sessionInfo