[gdal-dev] self-compiled gdal linking to old already-remove proj libs
Andreas Neumann
a.neumann at carto.net
Sat May 16 05:41:10 PDT 2020
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
More information about the gdal-dev
mailing list