Re: Error During PostGIS Build From Source on Linux

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Osahon Oduware <osahon(dot)gis(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Error During PostGIS Build From Source on Linux
Date: 2017-04-15 17:49:30
Message-ID: d91e5ff9-62d3-77e6-4dfd-666cb7e57021@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 04/14/2017 12:20 PM, Osahon Oduware wrote:
> Hi Adrian,
>

Something I meant to refer to earlier, it is considered bad etiquette to
cross post to multiple lists. It means in this case I have to remember
to drop the postgis list from my replies as I am not a member of that
list and I get a rejection notice if I forget.

> I installed Proj from source and I can confirm that the
> file libproj.so.12 is in its lib folder.

That directory would be?

>
> I have not been able to confirm if it is linked to postgis-2.3.so
> <http://postgis-2.3.so/> as I am away for Easter holiday.
>
> Just in case, how do I do the linking of libproj.so.12 to postgis-2.3.so
> <http://postgis-2.3.so/> as I believe this could be the cause of the
> error. Also, I tried earlier to copy the file to the PostgreSQL lib
> folder and this time when I try to run "CREATE EXTENSION postgis;" I get
> the initial error:
> ERROR: could not load library "/path/to/postgresql/lib/postgis-2.3.so
> <http://postgis-2.3.so/>": /path/to/postgresql/lib/postgis-2.3.so
> <http://postgis-2.3.so/>: undefined symbol: GEOSClipByRect

Probably going to involve dealing with ldconfig.

Look in /etc/ld.so.conf and see if the directory that contains
libproj.so.12 is in there?

>
> I will be glad if anyone could help with this.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2017-04-15 18:25:45 Re: Error During PostGIS Build From Source on Linux
Previous Message Moreno Andreo 2017-04-14 21:40:40 Re: Service outage: each postgres process use the exact amount of the configured work_mem [(AUTO-RE)SOLVED...]