GEOS requirement misstated

[robe]

I think there is a mismatch between our minimum GEOS requirement documentation and actual requirement. Need to verify and may have to do with topology needing newer version than the rest of PostGIS proper.

See comment from Gabrielle:

​http://gorthx.wordpress.com/2013/04/05/installing-postgresql-and-friends-from-source-on-ubuntu-12-04-precise-pangolin/comment-page-1/#comment-410

[strk]

From the configure script:

Topology requires GEOS version ≥ 3.3.2. Use —without-topology or install a newer GEOS.

[robe]

Ah okay then no problem. I was right. Though I didn't think topology tried to install if it had a lower GEOS.

I'll close out as a non-issue, but we probably should have one buildbot test against 3.2. Setting up debbie to do that now.

[robe]

I can't get this to work on Debbie even using

--with-topology

I think our configure is all screwy with how it handles custom configs

[robe]

I mean —without-topology

[robe]

related #2268

[robe]

I'll try to test on debbie later. Last I tried it failed miserably which is why I haven't gotten 3.2 regress testing going on debbie. Anyrate I think we DO have an issue. Which I might add would be solved if we dropped 3.2 support

[pramsey]

I'm totally not seeing this. I installed a too-low geos in my system path (/usr/local) and installed a good geos in a custom path (/opt/geos) and configured with the custom location, and it worked fine.

./configure --with-libintl-prefix=/opt/local \
 --with-libiconv-prefix=/opt/local --with-jsondir=/opt/local \
 --with-gettext=/opt/local \
 --with-geosconfig=/opt/geos/bin/geos-config

If I configure without the custom geos location, it fails, as it should, with the too-low geos.

[robe]

alright if it works for you good enough for me.