[gdal-dev] self-compiled gdal linking to old already-remove proj libs

[Andreas Neumann]

Hi,

Thank you both Jeff and Even.

Yes, apparently libspatialite was also self-compiled. I can renew that. 
That was the one linking against non-existant old libproj.

For libgeotiff I used the packaged one, which links against 
/usr/lib/x86_64-linux-gnu/libproj.so.15

Is it a problem if libgeotiff links against a different libproj than 
gdal? Should I also self-compile libgeotiff?

Thanks for your help! It helps me to solve the compile and link issues.

Andreas

Am 16.05.20 um 16:12 schrieb Jeff McKenna:
> 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
>
>