-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
proj4 error in installation #22
Comments
Try |
Thanks! |
I confirm the answer of carbonmetrics on ubuntu 16.04 |
With LinuxMint 18.1 and R version 3.4.3 (2017-11-30) , I had to follow this steps: 1º - sudo aptitude install libproj-dev libgdal-dev |
In Cent OS, |
While installing Following the procedure of @fodassecaralho (thanks 👍 ) could solve the prob with |
This is the exact answer that works perfectly for me |
I am having the same issue trying to built proj4 for R/4.0.2 on a CentOS 7.9 system. I have installed the proj and proj-devel packages which puts things in standard places (i.e. /usr/include and /usr/lib64). However i still keep getting this error: checking proj_api.h usability... yes *** Install PROJ library and if necessary set PKG_CPPFLAGS/PKG_LIBS accordingly.
Even if i set PKG_CPPFLAGS and PKG_LIBS to point to the standard spot, it still fails to build. Any thoughts? |
@MrDotOne any luck? I ran into the same issue |
@andrewrech and @MrDotOne I am running into a similar issue. Just wondered if you have tried installing gdal (in step 1 of #22 (comment))? I am resisting installing gdal as I don't want netcdf library conflicts on the machine I am currently on, but curious to know if that would solve the issue. |
@KayShelton, yes, I tried installing
confirming that the requested file was installed, and configuring PKG_CPPFLAGS/PKG_LIBS, but I receive the same error message as @MrDotOne. @hrbrmstr could you perhaps point the three of us in the right direction? Thanks
|
@ CentOS this helped me through:
Probably there are a few not needed. I presume that @jongmmm had either |
Thanks a lot @yhoogstrate. The answer was |
The text was updated successfully, but these errors were encountered: