-
-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to build with GEOS 3.6.0 #634
Comments
Unless someone provides a patch it's unlikely the maintainers will be providing support for the geos API changes in 3.6.0. Given the chance for memory leaks in any change, if someone did supply a patch it's unlikely it would be backported to 0.90.x. Long term we'd like to move away from geos, but this won't help with 0.90.x either. I'm leaving this open because
|
Found this related discussion: http://lists.osgeo.org/pipermail/geos-devel/2016-October/007573.html |
FYI, FreeBSD has already switched to geos 3.6.0. It's no more possible to build osm2pgsql there. |
FreeBSD user have submitted a patch to make it compile with geos 3.6.0, and it was confirmed to work. I'd like upstream comments though. |
Without testing I can't be positive, but I think that would break compilation on Geos 3.5 |
That would be likely. If they've broken an API, the code is likely to work on one of versions only. If that's a correct fix to 3.6.0, it could be upstreamed with proper |
I am the maintainer of the geos package in pkgsrc, and I am wondering if it's time to update to 3.6.1 from 3.5.1. From the pkgsrc viewpoint, a version of osm2pgsql that requires geos >= 3.6.0 is fine, since that's easy to express. Absent a released version of osm2pgsql (pkgsrc attempts to package only releases), I am inclined to hold off a bit on geos 3.6.1. |
There are no plans to officially support geos >= 3.6.0. We plan to get completely rid of geos instead. It might be a while, though, before an official release without geos is available. We are aware that this creates a problem for distributions. The problem is that it seems that the only viable way forward with geos 3.6 is to switch to the C API and that is about as much work as getting rid of it. |
Reported by naddy@ & sthen@, also see osm2pgsql-dev/osm2pgsql#634, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214819 and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216338
Suggested-by: [email protected] Upstream-bug: osm2pgsql-dev/osm2pgsql#634 Package-Manager: portage-2.3.0
Closed in #684, where we no longer support geos. For backports, anything which requires geos >= 3.6.0 is not an option, as earlier versions of geos must continue to work. An option which supports both >=3.6 and <3.6 is probably too invasive to be backported into a patch release, and would require extensive testing. |
(I'm the maintainer of the geos package within pkgsrc, and have been delaying updating to 3.6 for most of a year. I've been distracted, and returned to this because geos 3.7 is about to be released.) Seeing this bug closed, I just tried to build the latest release (0.92.1) without geos, and it failed, which on reading the README wasn't surprising. Am I correct that there is no release without geos (or that works with 3.6)? Any timeline for one (presumably 0.94)? |
Yes.
No timeline, but probably quite soon. We're reviewing if we're ready. |
I couldn't find any other reference to fixing it or removing geos entirely when I searched the repo. Is there any update on this? Thank you. |
It's explicitly posted in this issue, specifically in #634 (comment):
|
Apologies for missing that. Thanks for your response. |
GEOS 3.6.0 has been released, but unfortunately osm2pgsql fails to build with it:
This change seems to be the culprit.
The text was updated successfully, but these errors were encountered: