-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install issue on RHEL7 #1022
Comments
Did you check this? |
Thanks Edzer, I already uninstalled previous versions of gdal. I manually deleted libgeos files from other locations and the error is: Am i missing something? |
The GEOS error suggests that configure detected GEOS 3.7.0, but that this was not available at link time - again multiple versions and wrong setup; the following GDAL error a broken setup. I'm not familiar with RHEL-based distros. Reboot? |
You were right, tried with a fresh install and this comment: #844 (comment) |
In Mac OS environment (Catalina 10.15.4) with Anaconda I got this error when I first tried to install the SF package using "install.packages". I was able to resolve it by directly installing packages using conda command `— create a new R environment “r_gis” conda create -n r_gis --channel conda-forge python=3.7 gdal=3.0.4 libgdal=3.0.4 r-rgdal=1.4_8 r-gdalutils=2.0.3.2 r-sf udunits2 rstudio activate r_gis |
The following error occurs when trying to install the sf package in Oracle Linux 7 (based on RHEL7) :
sh: line 1: 31803 Segmentation fault (core dumped) '/usr/lib64/R/bin/R' --no-save --slave 2>&1 < '/tmp/RtmpPgbsqb/file7a152bf3a26a'
*** caught segfault ***
address 0x8, cause 'memory not mapped'
The install command was:
install.packages("sf",
type = "source",
configure.args = paste0("--with-gdal-config=","/usr/local/bin/gdal-config"),
repos = "http://cran.rstudio.com"
,verbose=T
,keep_outputs = T)
We installed GDAL (2.4.1) from source because binaries are not available for versions above 1.14 on RHEL.
Both PROJ (4.8.0-4) and GEOS (3.4.2-2) were installed from epel.
The text was updated successfully, but these errors were encountered: