PG_Sphere
Gandalf the Gray
pjduplooy.gis at gmail.com
Sun Oct 13 22:59:16 PDT 2024
Thanks Regina.
I appreciate it!!
Pieter
On Mon, Oct 14, 2024 at 7:46 AM Regina Obe <lr at pcorp.us> wrote:
> Pieter,
>
>
>
> I’ve made a lot of progress. I isolated the offending line and remarked
> it out
> https://github.com/postgrespro/pgsphere/blob/master/src/output.c#L163
> for now as discussed in -
> https://github.com/postgrespro/pgsphere/issues/130 Didn’t want to
> introduce a windows only function to compensate unless I have to.
>
>
>
> It’s not ideal but at least you can do CREATE EXTENSION and some other
> things. You can find the binaries in -
> https://winnie.postgis.net/download/windows/pg17/buildbot/extras/
>
>
>
> I’ll let you know once I have a build that regresses cleanly.
>
>
>
> Just for reference this is the regression results:
>
>
>
> ok 1 - init 127 ms
>
> ok 2 - version 37 ms
>
> ok 3 - tables 866 ms
>
> ok 4 - points 49 ms
>
> ok 5 - euler 43 ms
>
> ok 6 - circle 49 ms
>
> ok 7 - line 41 ms
>
> ok 8 - ellipse 58 ms
>
> ok 9 - poly 104 ms
>
> ok 10 - path 52 ms
>
> ok 11 - box 76 ms
>
> ok 12 - index 150 ms
>
> ok 13 - contains_ops 78 ms
>
> ok 14 - contains_ops_compat 80 ms
>
> not ok 15 - bounding_box_gist 1396 ms
>
> # (test process exited with exit code 2)
>
> not ok 16 - gnomo 35 ms
>
> # (test process exited with exit code 2)
>
> not ok 17 - epochprop 34 ms
>
> # (test process exited with exit code 2)
>
> not ok 18 - contains 34 ms
>
> # (test process exited with exit code 2)
>
> not ok 19 - overlaps 33 ms
>
> # (test process exited with exit code 2)
>
> not ok 20 - spoint_brin 1247 ms
>
> # (test process exited with exit code 2)
>
> not ok 21 - sbox_brin 33 ms
>
> # (test process exited with exit code 2)
>
> not ok 22 - selectivity 33 ms
>
> # (test process exited with exit code 2)
>
> not ok 23 - knn 1699 ms
>
> not ok 24 - output_precision 42 ms
>
> not ok 25 - gist_support 41 ms
>
>
>
> Thanks,
>
> Regina
>
>
>
> *From:* Gandalf the Gray <pjduplooy.gis at gmail.com>
> *Sent:* Friday, October 11, 2024 2:48 AM
> *To:* Regina Obe <lr at pcorp.us>; postgis-devel at lists.osgeo.org
> *Subject:* Re: PG_Sphere
>
>
>
> Hi Regina.
>
>
>
> Any progress with this issue?
>
>
>
>
>
> On Wed, Oct 9, 2024 at 5:36 PM Regina Obe <lr at pcorp.us> wrote:
>
> That’s what I was running into. But that looks to be your PostgreSQL
> windows install.
>
> Works fine under my mingw64 postgresql built.
>
>
>
> No clue at the moment why 17 doesn’t work but the others work fine.
>
> I was going to take a deeper look later this week.
>
>
>
> Thanks,
>
> Regina
>
>
>
> *From:* Gandalf the Gray <pjduplooy.gis at gmail.com>
> *Sent:* Wednesday, October 9, 2024 11:04 AM
> *To:* Regina Obe <lr at pcorp.us>; postgis-devel at lists.osgeo.org
> *Subject:* Re: PG_Sphere
>
>
>
> Hi Regina
>
>
>
> I could not load PG_Sphere.
>
>
>
> I have extracted the archive into my PG folder, and restarted PG. Upon
> create extension, I get "could not load library C:/Program
> Files/PostgreSQL/17/lib/pg_sphere.dll:; The specified procedure could not
> be found."
>
>
>
> Any clue?
>
>
>
> On Wed, Oct 9, 2024 at 3:50 PM Gandalf the Gray <pjduplooy.gis at gmail.com>
> wrote:
>
> Thanks Regina.
>
>
>
> Appreciate it!
>
>
>
> On Wed, Oct 9, 2024 at 3:46 PM Regina Obe <lr at pcorp.us> wrote:
>
> I’ve put the binaries I built here:
>
>
>
> https://winnie.postgis.net/download/windows/pg17/buildbot/extras/
>
>
>
> As far as compiling under mingw, there isn’t anything special I had to do
> aside from my usual specifying the postgresql version path.
>
> So instructions they have assuming you’ve already installed autoconf,
> gcc++ etc should be sufficient.
>
>
>
> export OS_BUILD=64
>
> export PROJECTS=/projects
>
> export GCC_TYPE=
>
> export PG_VER=17
>
> export PGPATH=${PROJECTS}/postgresql/rel/pg${PG_VER}w${OS_BUILD}${GCC_TYPE}
>
> export PATH="${PGPATH}/bin:${PGPATH}/lib:${PATH}"
>
>
>
> make USE_HEALPIX=0
>
> make USE_HEALPIX=0 install
>
> make installcheck USE_HEALPIX=0
>
>
>
> I haven’t tried compiling with HEALPIX since that itself when I tried had
> additional dependencies to compile which I hadn’t gone thru to investigate.
>
>
>
> Let me know if you need further help like setting up your tool chain.
>
>
>
> Thanks,
>
> Regina
>
>
>
>
>
>
>
>
>
> *From:* Gandalf the Gray <pjduplooy.gis at gmail.com>
> *Sent:* Wednesday, October 9, 2024 9:13 AM
> *To:* Regina Obe <lr at pcorp.us>; postgis-devel at lists.osgeo.org
> *Subject:* Re: PG_Sphere
>
>
>
> Hi Regina.
>
>
>
> Would it be possible to send me the Mingw build, or to guide me through
> the build process, as I have MingW setup for Mame.
>
>
>
> On Tue, Oct 8, 2024 at 5:00 PM Gandalf the Gray <pjduplooy.gis at gmail.com>
> wrote:
>
> Thank you Regina!
>
>
>
> On Tue, Oct 8, 2024 at 3:59 PM Regina Obe <lr at pcorp.us> wrote:
>
> I’m troubleshooting why the PG17 ones I built (and that regressed fine
> under Mingw) didn’t seem to install under PG17 VC++ build.
>
> In all cases before, if I was able to get things to compile under MingW
> they work fine in VC++ builds.
>
>
>
> Once I figure that out (whether it’s my fault or something in the pgsphere
> code), I’ll deploy those binaries.
>
> BTW once they tag the 1.5.2 (which has the fix to build under mingw64
> https://github.com/postgrespro/pgsphere/pull/123 ), I’m planning to
> include it in the PostGIS windows bundles.
>
>
>
> Thanks,
>
> Regina
>
>
>
> *From:* Gandalf the Gray <pjduplooy.gis at gmail.com>
> *Sent:* Tuesday, October 8, 2024 6:42 AM
> *To:* postgis-devel at lists.osgeo.org
> *Subject:* PG_Sphere
>
>
>
> Hi Regina.
>
>
>
> Thanks a million for PG_Sphere binaries for Windows!!.
>
>
>
> Any chance of a PG 17 version?
>
>
>
> Pieter
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20241014/4eec4a8a/attachment-0001.htm>
More information about the postgis-devel
mailing list