<div dir="ltr"><div>Hi Even,</div><div><br></div><div>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)<br></div><div><br></div><div>I ran "./configure" successfully with this statement:</div><div>./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</div><div><br></div><div>Then I try to run "Make -j8" and I get an error extracted below (see attachment for more detailed error):</div><div>/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)<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_open'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyEnd'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultErrorMessage'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQstatus'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetNoticeProcessor'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQnfields'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetvalue'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQclear'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetlength'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfmod'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftablecol'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQconnectdb'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQcmdStatus'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftable'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQntuples'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexecParams'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfname'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfinish'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_close'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQerrorMessage'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_read'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyData'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_write'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetResult'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetisnull'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQescapeStringConn'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexec'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_creat'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetClientEncoding'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftype'<br>/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultStatus'<br>collect2: error: ld returned 1 exit status<br>make[1]: *** [gdalserver] Error 1<br></div><div></div><div><br></div><div>Please, could you point me to the likely cause of this error. I look forward to hearing from you.<br></div><div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 25, 2018 at 12:43 PM, Osahon Oduware <span dir="ltr"><<a href="mailto:osahon.gis@gmail.com" target="_blank">osahon.gis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Even,</div><div><br></div><div>Thanks a lot. This is great news! I will start investigating the fix for Out-DB rasters. I will keep you posted. Great work!<br></div></div><div class="gmail-HOEnZb"><div class="gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 25, 2018 at 10:26 AM, Even Rouault <span dir="ltr"><<a href="mailto:even.rouault@spatialys.com" target="_blank">even.rouault@spatialys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:<br>
> Hi Even,<br>
> <br>
</span><span>> I want to find out if this GDAL fix will be release by the end of June. I<br>
> use PostGIS version 2.3.2 at present and I will be building from source.<br>
<br>
</span>Yes, this is in the release notes of the release candidate of GDAL 2.3.1 that <br>
was published last Friday:<br>
<a href="https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News" rel="noreferrer" target="_blank">https://trac.osgeo.org/gdal/wi<wbr>ki/Release/2.3.1-News</a><br>
<div class="gmail-m_7839548283890936343HOEnZb"><div class="gmail-m_7839548283890936343h5"><br>
-- <br>
Spatialys - Geospatial professional services<br>
<a href="http://www.spatialys.com" rel="noreferrer" target="_blank">http://www.spatialys.com</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>