Closed Zalkota closed 4 years ago
I’m installing the GDAL, Geos, Proj4 libraries from source ...
Then why you install PROJ and GEOS (headers, etc.) from the packages too?
sudo yum -y install make automake gcc gcc-c++ libcurl-devel proj-devel geos-devel s3cmd
I may be missing something, but that script does not do anything about GDAL itself, no build steps, just bundling build output:
cd /usr/local/gdal
tar zcvf "/tmp/gdal-${GDAL_VERSION}.tar.gz" *
Finally, I don't think this is GDAL issue at all, but it seems to be GeoDjango, Linux distribution or environment specific configuration issue.
I don't think this is GDAL issue at all
me too. Closing on that basis
I’m installing GDAL on a Amazon Elastic Beanstalk EC2 and try to run a GeoDjango web application, but it returns an error about missing C library’s. Which is very odd. I’m installing the GDAL, Geos, Proj4 libraries from source via this guide and they are being stored in /usr/local/geos, /usr/local/gdal, /usr/local/proj4 on the EC2.
Environment Paths on AWS EC2: $LD_Library: /usr/local/proj4/lib:/usr/local/geos/lib:/usr/local/gdal/lib:$LD_LIBRARY_PATH
$GDAL_LIBRARY_PATH: /usr/local/gdal/lib/libgdal.so
Expected behavior and actual behavior.
Expected behavior: Django GeoDjango web application runs as it does in my Ubuntu 18 environment.
actual behavior:
Error: OSError: libjson-c.so.3: cannot open shared object file: No such file or directory
Steps to reproduce the problem.
Apache attempts to run my Django Application (Which runs successfully on Ubuntu 18), apache returns the missing library error
Operating system
Amazon Linux Python 2.9.5 Elastic Beanstalk EC2
GDAL version and provenance
GDAL_VERSION=2.4.4 GEOS_VERSION=3.6.4 PROJ4_VERSION=5.2.0
Stored in /usr/local/gdal, /usr/local/geos, /usr/local/proj4.