[postgis-users] postgis_raster undefined symbol error

[Andy Knight via postgis-users]

I'm trying to create a postgis_raster extension and I'm getting the following error:

CREATE EXTENSION postgis_raster;

ERROR:  could not load library "/usr/pgsql-13/lib/postgis_raster-3.so": /usr/libspatialite50/lib/libspatialite.so.8: undefined symbol: GEOSHilbertCode_r

The instance is running on Rocky 8 linux details as below;:

NAME="Rocky Linux"

VERSION="8.8 (Green Obsidian)"

postgis31_13-utils-3.1.9-1.rhel8.x86_64

postgis31_13-devel-3.1.9-1.rhel8.x86_64

postgis31_13-client-3.1.9-1.rhel8.x86_64

postgis31_13-3.1.9-1.rhel8.x86_64

postgis31_13-docs-3.1.9-1.rhel8.x86_64

 

postgresql13-server-13.12-1PGDG.rhel8.x86_64

 

[Greg Troxel via postgis-users]

Andy Knight via postgis-users <postgi...@lists.osgeo.org> writes:

> I'm trying to create a postgis_raster extension and I'm getting the
> following error:
>
> CREATE EXTENSION postgis_raster;
>
> ERROR: could not load library "/usr/pgsql-13/lib/postgis_raster-3.so":
> /usr/libspatialite50/lib/libspatialite.so.8: undefined symbol:
> GEOSHilbertCode_r
>
> The instance is running on Rocky 8 linux details as below;:

You are having a Rocky problem not a postgis problem, almost certainly,
and I would raise this with the Rocky geo packagers.

I will assume your system is in a valid state per Rocky doctrine. I am
not the least bit confident, but if you aren't sure you should step into
Rocky land from postgis and ensure that before proceeding.

To debug this, you're going to have to either

use ldd and nm -g or objdump to find out what symbols are defined and
needed

understand the build environment. It looks like postgis was built
against a different version of geos than spatialite. In a correct
packaging system, this won't happen, but I have no clue how Rocky
intends to do this.

> NAME="Rocky Linux"
> VERSION="8.8 (Green Obsidian)"
> postgis31_13-utils-3.1.9-1.rhel8.x86_64
> postgis31_13-devel-3.1.9-1.rhel8.x86_64
> postgis31_13-client-3.1.9-1.rhel8.x86_64
> postgis31_13-3.1.9-1.rhel8.x86_64
> postgis31_13-docs-3.1.9-1.rhel8.x86_64

There are a lot of other packages that matter and you left them out.
But again this is a Rocky issue.
_______________________________________________
postgis-users mailing list
postgi...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users

[Regina Obe via postgis-users]

This problem usually happens if for some reason you have two versions of GEOS installed  and the older one is being loaded.

Might be a packaging issue.  I’ve cc’d the pgsql-yum mailing list for guidance.

 

Thanks,

Regina

[Devrim Gündüz via postgis-users]

Hi,

On Tue, 2023-10-10 at 09:12 -0400, Tim Kempisty wrote:
> All of the latest packages for Rocky/RHEL8 on PGDG have dependency
> problems with PostGIS, GDAL, GEOS, and GDAL's python support
> packages. 

I believe I fixed this issue. Please see 3.6.4-4 packages.

Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR

[Devrim Gündüz via postgis-users]

Hi,

On Thu, 2023-10-12 at 03:39 +0100, Devrim Gündüz wrote:
> I believe I fixed this issue. Please see 3.6.4-4 packages.

err. 3.6.4-5.

[Andy Knight via postgis-users]

Thanks for all the support. I've updated the rpms to the recent 3.1.9-2 and I'm now able to create the extension.

[Devrim Gündüz via postgis-users]

Hi,

On Thu, 2023-10-12 at 14:07 +0100, Andy Knight wrote:
> Thanks for all the support. I've updated the rpms to the recent 3.1.9-
> 2 and I'm now able to create the extension.

Thanks!

Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR