Closed akhst7 closed 4 years ago
...the complier does not see Makevars. Is there any way to let the complier point to the Makevars instead of Makeconf?
Sorry but you can't point a compiler to a Makevars or Makeconf. That doesn't make sense.
So you know that the settings in /usr/local/Cellar/r/3.6.2/lib/R/etc/Makeconf
are bad and you're trying to override them with your own settings? Doesn't that simply mean that your R installation is broken? Note that you could always try to repair it by fixing the settings in /usr/local/Cellar/r/3.6.2/lib/R/etc/Makeconf
(why keep the current settings if you know they don't work) even though it would probably be more useful to understand why you ended up with a broken R installation in the first place.
In any case, that doesn't sound like an Rhtslib problem.
Also any reason why you didn't install R official binaries for Mac or the Rhtslilb Mac binary that is provided by Bioconductor? Rhtslib is a Bioconductor package and the standard way to install a Bioconductor package is with:
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("Rhtslib")
On a Mac this will install the Mac binary.
See https://github.com/Bioconductor/Rhtslib/issues/14#issuecomment-547097988 for why you should use the "official R Mac binary".
No news = good news (I guess)
Trying to install the latest Rhtslib 1.7 but it fails. A following is an excerpt of the installer output;
I think the issue is clang is not using the correct arguments for OSX Catalina which I have it in ~/.R/Makevars but for some reasons, the complier does not see Makevars. Is there any way to let the complier point to the Makevars instead of Makeconf ?