ogr2ogr links to the wrong libproj.so on openSuSE

[stephan66]

On openSuSE 11.4 (64-bit system)

ogr2ogr fails, complaining in can't find libproj.so.

rpm packages containing ogr2ogr and libproj.so where obtained from: ​http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/

The rpm package libproj0 installs /usr/lib64/libproj.so.0.7.0, and creates a link:

/usr/lib64/libproj.so.0 -> /usr/lib64/libproj.so.0.7.0

However, ogr2ogr expects to find libproj.so.

Ismail Dönmez from SuSE informs me that there is an official SuSE policy to NOT prove libraries without version numbers (like "libproj.so").

Please see:

​http://en.opensuse.org/openSUSE:Shared_library_packaging_policy

for more information and the background to this policy.

So, it looks like ogr2ogr should be looking for libproj.so.* on an openSuSE system instead of libproj.so

[Even Rouault]

You can pass the message to SuSe mainteners that a better alternative for them would be to build with the --with-static-proj4 flag for ./configure (which contrary to the name can link against the shared library version of proj ;-)) . The dynamic loading of libproj.so is something mostly historical.

[Stephan66]

Tested with recent 64-bit gdal package from ​http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/

Bug in ogr2ogr still present in gdal rpm version 1.9.1-2.3.

[Even Rouault]

This is not the openSuse bug tracker here ;-) I'm not sure if this will be fixed here. Perhaps you could suggest to the Suse maintener to patch ogr/ogrct.cpp to link to "libproj.so.0" (I think some other Linux distro do this now) instead of "libproj.so", or just build their package --with-static-proj4 as suggested.

[Jukka Rahkonen]

Closing as invalid.