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

Поиск
Список
Период
Сортировка
От Christoph Berg
Тема Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so:undefined symbol: geod_polygon_init
Дата
Msg-id 20190221164652.GF5238@msg.df7cb.de
обсуждение исходный текст
Ответ на Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so:undefined symbol: geod_polygon_init  (Justin Pryzby <pryzby@telsasoft.com>)
Список pgsql-pkg-yum
Re: Justin Pryzby 2019-02-21 <20190221163030.GY28750@telsasoft.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@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


В списке pgsql-pkg-yum по дате отправления:

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: [PostgreSQL YUM Repository - Bug #3710] (Resolved) RHEL7postgresql11 postgis2.5 fails with /usr/pgsql-11/lib/postgis-2.5.so:undefined symbol: geod_polygon_init
Следующее
От: Devrim Gündüz
Дата:
Сообщение: Re: Broken PG10 packages for F28