Red Hat Bugzilla – Bug 979179
Postgis 2.0 ships static libraries
Last modified: 2015-08-02 19:58:01 EDT
I just noticed the 2.0 packages contain:
You need a -devel sub-package, and a -static if you want to keep the static library.
postgis.x86_64: W: undefined-non-weak-symbol /usr/lib64/liblwgeom-2.0.3.so lwgeom_init_allocators
postgis.x86_64: W: shared-lib-calls-exit /usr/lib64/liblwgeom-2.0.3.so exit@GLIBC_2.2.5
postgis.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/pgsql2shp ['/usr/lib64']
postgis.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/raster2pgsql ['/usr/lib64']
postgis.x86_64: W: spurious-executable-perm /usr/include/liblwgeom.h
postgis.x86_64: E: incorrect-fsf-address /usr/share/doc/postgis-2.0.3/COPYING
Also, I think shipping liblwgeom in a separate liblwgeom or postgis-lib sub-package would allow us to avoid a circular dependency on gdal.
Please delete the two static files so we can close this ticket. The point Orion mentions here is a lot more critical though.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
Please address this issue. At least the static library part is really easy.
Thanks for reporting. I have removed static libraries from package. The shared libraries seems to be sufficient.
Change of the liblwgeom into separate package seems to be reasonable. In contrary, it seems to be integral part of postgis.