[gdal-dev] [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware osahon.gis at gmail.com
Tue Jun 26 14:06:38 PDT 2018


Hi All,

Can anyone help with the error in my previous mail?

On Jun 26, 2018 12:39 PM, "Osahon Oduware" <osahon.gis at gmail.com> wrote:

> Hi Even,
>
> I was trying to build GDAL 2.3.1 from source into PostgreSQL 9.6.9 that
> was built successfully from source, but I am getting an error when running
> "make -j8" (see attachment)
>
> I ran "./configure" successfully with this statement:
> ./configure --prefix=/home/nagispg/local/gdal213
> --with-pg=/home/nagispg/local/pgsql/bin/pg_config
> --with-mrsid=/home/nagispg/local/src/MrSID_DSDK-9.5.4.
> 4703-rhel6.x86-64.gcc531/Raster_DSDK
>
> Then I try to run "Make -j8" and I get an error extracted below (see
> attachment for more detailed error):
> /bin/ld: warning: libpq.so.5, needed by /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so,
> not found (try using -rpath or -rpath-link)
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `lo_open'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQputCopyEnd'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQresultErrorMessage'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQstatus'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQsetNoticeProcessor'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQnfields'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQgetvalue'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQclear'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQgetlength'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQfmod'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQftablecol'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQconnectdb'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQcmdStatus'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQftable'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQntuples'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQexecParams'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQfname'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQfinish'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `lo_close'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQerrorMessage'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `lo_read'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQputCopyData'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `lo_write'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQgetResult'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQgetisnull'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQescapeStringConn'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQexec'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `lo_creat'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQsetClientEncoding'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQftype'
> /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference
> to `PQresultStatus'
> collect2: error: ld returned 1 exit status
> make[1]: *** [gdalserver] Error 1
>
> Please, could you point me to the likely cause of this error. I look
> forward to hearing from you.
>
>
> On Mon, Jun 25, 2018 at 12:43 PM, Osahon Oduware <osahon.gis at gmail.com>
> wrote:
>
>> Hi Even,
>>
>> Thanks a lot. This is great news! I will start investigating the fix for
>> Out-DB rasters. I will keep you posted. Great work!
>>
>> On Mon, Jun 25, 2018 at 10:26 AM, Even Rouault <
>> even.rouault at spatialys.com> wrote:
>>
>>> On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:
>>> > Hi Even,
>>> >
>>> > I want to find out if this GDAL fix will be release by the end of
>>> June. I
>>> > use PostGIS version 2.3.2 at present and I will be building from
>>> source.
>>>
>>> Yes, this is in the release notes of the release candidate of GDAL 2.3.1
>>> that
>>> was published last Friday:
>>> https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News
>>>
>>> --
>>> Spatialys - Geospatial professional services
>>> http://www.spatialys.com
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20180626/b206669f/attachment.html>


More information about the gdal-dev mailing list