Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7 postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so: undefined symbol: geod_polygon_init

From: Christoph Berg <myon(at)debian(dot)org>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-pkg-yum(at)postgresql(dot)org
Subject: Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7 postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so: undefined symbol: geod_polygon_init
Date: 2019-02-21 16:46:52
Message-ID: 20190221164652.GF5238@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-yum

Re: Justin Pryzby 2019-02-21 <20190221163030(dot)GY28750(at)telsasoft(dot)com>
> On Thu, Feb 21, 2019 at 02:26:06PM +0100, Christoph Berg wrote:
> > Why does postgis-2.4.so even "see" the geos37 package?
> >
> > > [pryzbyj(at)template0 ~]$ ldd /usr/pgsql-11/lib/postgis-2.4.so
> > > libgeos_c.so.1 => /usr/geos36/lib64/libgeos_c.so.1 (0x00007f3e50e6e000)
> > > libgeos-3.6.2.so => /usr/geos36/lib64/libgeos-3.6.2.so (0x00007f3e4f12e000)

Ah, I'm spotting this only now: The problem is that libgeos_c.so.1
doesn't have "3.6" in its SONAME, so a 3.7-linked postgis.so will try
to load libgeos_c.so.1, find the 3.6 one, and explode.

Or is libgeos_c.so.1 supposed to be independent from the geos version?

Christoph

In response to

Browse pgsql-pkg-yum by date

  From Date Subject
Next Message Devrim Gündüz 2019-02-24 01:10:49 Re: Broken PG10 packages for F28
Previous Message Justin Pryzby 2019-02-21 16:30:30 Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7 postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so: undefined symbol: geod_polygon_init