Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-pkg-yum-owner+archive@lists.postgresql.org>)
	id 1gwrUv-00069q-Ax
	for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 21 Feb 2019 16:46:57 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-pkg-yum-owner+archive@lists.postgresql.org>)
	id 1gwrUu-0003e4-09
	for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 21 Feb 2019 16:46:56 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1gwrUt-0003dx-RB
	for pgsql-pkg-yum@lists.postgresql.org; Thu, 21 Feb 2019 16:46:55 +0000
Received: from feynman.df7cb.de ([195.49.152.168])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1gwrUr-0003ed-TJ
	for pgsql-pkg-yum@postgresql.org; Thu, 21 Feb 2019 16:46:55 +0000
Received: from msg.df7cb.de (unknown
 [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client did not present a certificate)
	by feynman.df7cb.de (Postfix) with ESMTPSA id 4450k4664Hz3F1k;
	Thu, 21 Feb 2019 17:46:52 +0100 (CET)
Date: Thu, 21 Feb 2019 17:46:52 +0100
From: Christoph Berg <myon@debian.org>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-pkg-yum@postgresql.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
Message-ID: <20190221164652.GF5238@msg.df7cb.de>
Mail-Followup-To: Christoph Berg <myon@debian.org>,
	Justin Pryzby <pryzby@telsasoft.com>, pgsql-pkg-yum@postgresql.org
References: <redmine.issue-3710.20181018173810@postgresql.org>
 <redmine.journal-14074.20181210113352.5ccd98437e7314f6@postgresql.org>
 <20181210150643.GF4848@telsasoft.com>
 <20181219202107.GA5406@telsasoft.com>
 <20190107215410.GA22493@telsasoft.com>
 <20190221132606.GC5238@msg.df7cb.de>
 <20190221163030.GY28750@telsasoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190221163030.GY28750@telsasoft.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
List-Id: <pgsql-pkg-yum.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-pkg-yum@lists.postgresql.org>
List-Owner: <mailto:pgsql-pkg-yum-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-pkg-yum>
Precedence: bulk

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