zdk123 / SpiecEasi

Sparse InversE Covariance estimation for Ecological Association and Statistical Inference
GNU General Public License v3.0
196 stars 68 forks source link

Error in installing packages #253

Open jlche opened 10 months ago

jlche commented 10 months ago

Hi, I am trying to install the package on my laptop (macOS Monterey 12.7.2) using the RStudio (Version 2023.12.0), but it failed to visit and download via the routine as shown below. May I try the other way or do you know how to solve this error? Thanks a lot.

install_github("zdk123/SpiecEasi") Downloading GitHub repo zdk123/SpiecEasi@HEAD ── R CMD build ────────────────────────────────────────────────────────────────────────────────────────────── ✔ checking for file ‘/private/var/folders/57/435jclf55xx08_k5bhcr6j940000gn/T/RtmpHLktoK/remotes370e29da7798/zdk123-SpiecEasi-5f396da/DESCRIPTION’ (355ms) ─ preparing ‘SpiecEasi’: ✔ checking DESCRIPTION meta-information ... ─ cleaning src ─ checking for LF line-endings in source and make files and shell scripts ─ checking for empty or unneeded directories Removed empty directory ‘SpiecEasi/inst’ ─ looking to see if a ‘data/datalist’ file should be added ─ building ‘SpiecEasi_1.1.3.tar.gz’

JiatingH commented 10 months ago

It works for me in https://github.com/zdk123/SpiecEasi/issues/217#issuecomment-1489172072

jlche commented 10 months ago

It has been solved. create folder name .R ; then create subfolder name it with Makevars, input below code into Makevars: FC = /usr/local/gcc/bin/gfortran E77 = /usr/local/opt/gcc/bin/gfortran FLIBS = -L/usr/local/opt/gcc/lib

jlche commented 10 months ago

It has been solved. create folder name .R ; then create subfolder name it with Makevars, input below code into Makevars: FC = /usr/local/gcc/bin/gfortran E77 = /usr/local/opt/gcc/bin/gfortran FLIBS = -L/usr/local/opt/gcc/lib

    ------------------ Original ------------------ From: @.>; Date:  Thu, Feb 1, 2024 03:04 PM To: @.>; Cc: @.>; @.>; Subject:  Re: [zdk123/SpiecEasi] Error in installing packages (Issue #253)

 

I have encountered the same issue. Have you managed to resolve it?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>