Hi Andreas,
I have been in your exact situation before. What's happening is that a
GDAL dependency lib is still pointing to the old libproj version.
Please check:
ldd /usr/local/lib/libgdal.so | grep geotiff
and then ldd to the exact path of the geotiff lib, and look at
which libproj is linked to
and do the same for spatialite:
ldd /usr/local/lib/libgdal.so | grep spatialite
and then ldd to the exact path of the spatialite lib, and look at
which libproj is linked to
I bet that is what happening in your case also. If I am correct, then
you have to recompile those libraries and point to PROJ in /usr/local/
Cheers from across the ocean.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://gatewaygeo.com/
On 2020-05-16 9:41 a.m., Andreas Neumann wrote:
Hi,
After my upgrade of Ubuntu 18.04 to 20.04 I am also renewing all my
self-compiled "geo" libraries, such as proj, geos and gdal.
I removed old proj libs in /usr/local/lib then compiled and installed
the newest proj 7.0.1.
But now I am struggling with gdal - it always tries to link to old,
already removed libproj versions. When I do
ldd /usr/local/lib/libgdal.so | grep proj
I get
libproj.so.19 => /usr/local/lib/libproj.so.19 (0x00007fbaff612000)
libproj.so.15 => /usr/lib/x86_64-linux-gnu/libproj.so.15
(0x00007fbafd84e000)
libproj.so.12 => not found
The libproj.so.12 was removed by me, libproj.so.19 and libproj.so.15
probably came through some Ubuntu dependency.
How I can I tell the gdal configuration not to link to the already
removed libproj.so.12 ? And maybe also ignore the libproj.so.15 version?
Thanks for any help!
Andreas
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
