<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Paul and others,</p>
<p>Ok, so that issue with the wrong display of the PROJ version
number when calling 'postgis_full_version' after the upgrade of
PROJ from 6.3.1 to 7.2.1 using the UbuntuGIS repository available
version, is insignificant.</p>
<p>Is there anything else you want me to do? Even if I had the
experience, I do not have the infrastructure to debug PostGIS /
PROJ or anything else involved, except for the PostgreSQL /
PostGIS install on Ubuntu. You posted a GitHub link to a C file
(<a class="moz-txt-link-freetext" href="https://gist.github.com/pramsey/493b2490a8736fd8c00e30efa62e4ec3">https://gist.github.com/pramsey/493b2490a8736fd8c00e30efa62e4ec3</a>),
but I am unsure what to do with it. How do I run this?<br>
</p>
<p>And what is the status of the speculation about a possible
compiler optimization setting issue with PROJ 7.2.1 as available
from the UbuntuGIS apt repository? Is there any new information
about this?</p>
<p>Marco<br>
</p>
<div class="moz-cite-prefix">Op 30-4-2021 om 17:16 schreef Paul
Ramsey:<br>
</div>
<blockquote type="cite"
cite="mid:ECB52A99-5D48-4F40-B898-3ECA81DA261C@cleverelephant.ca">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 30, 2021, at 1:05 AM, Marco Boeringa <<a
href="mailto:marco@boeringa.demon.nl" class=""
moz-do-not-send="true">marco@boeringa.demon.nl</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="caret-color: rgb(0, 0, 0);
font-family: Helvetica; font-size: 12px; font-style:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Lastly, I am still a bit worried
about the fact that 'SELECT postgis_full_version()'
returns the old '6.3.1' PROJ version number after
upgrading PROJ to '7.2.1'. Is there any logical
explanation for this, e.g. 'postgis_full_version' only
ever returning the version number of the PROJ it was
originally compiled against, so never displaying the
upgrade?</span></div>
</blockquote>
</div>
<br class="">
<div class="">Sure, it’s fairly common, all you need is a library
where the version information is communicated via compile-time
#defines rather than a run-time getversion() function. Or a
library that does both (like proj) and the implementing
application uses the #defines. Early proj4 only had #defines, so
it wouldn’t be surprising to find apps that still use them, even
though modern proj has a runtime proj_version() available.</div>
<div class=""><br class="">
</div>
<div class="">P</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
postgis-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/postgis-devel">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a>
</pre>
</blockquote>
</body>
</html>