Opened 10 years ago
Closed 9 years ago
#44124 closed defect (fixed)
postgis2: fatal error: 'json/json.h' file not found
| Reported by: | joubertdj@… | Owned by: | Veence (Vincent) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.0 |
| Keywords: | Cc: | cooljeanius (Eric Gallager) | |
| Port: | postgis2 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Dear all,
I am using QGIS.
After I upgraded to Macports 2.3 I did a "sudo port upgrade outdated"
The only one that fails so far is Postgis2, it fails in the log file saying that it is looking for a JSON header ...
Best regards,
Dawie
Attachments (1)
Change History (7)
Changed 10 years ago by joubertdj@…
comment:1 Changed 10 years ago by Veence (Vincent)
Ok, I stumbled on that error two or three days ago. The json-c version provided by Macports is obviously either outdated or too recent for PostGIS/GDAL. I'll figure out a workaround.
comment:2 Changed 10 years ago by Veence (Vincent)
Should be fixed in r121330, but I had to disable JSON support (contrarily to GDAL, PostGIS does not embed its own JSON code).
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Keywords: | Postgis2 json build fail removed |
| Milestone: | MacPorts 2.3.1 |
| Owner: | changed from macports-tickets@… to vince@… |
| Port: | postgis2 added; Postgis2 removed |
| Summary: | Postgis2 - Upgrade Failure ... Looking for JSON Header? → postgis2: fatal error: 'json/json.h' file not found |
The fix might be as simple as changing the path to the header; the most noticeable change in the latest version of json-c is a renaming and rearranging of files.
Has this problem been reported to the developers of postgis2 so that they can fix it? If so, please mention the URL of the upstream bug report.
comment:4 Changed 10 years ago by Veence (Vincent)
Ryan, there is more in the new version of Json-C that a simple reorganization of file. Some API that were deprecated have been removed, and it seems the PostGIS code was using at least one of them. Upstream is aware of this caveat http://trac.osgeo.org/postgis/ticket/2723, and it should be corrected in 2.1.4. Meanwhile, I can try to apply one of the proposed patches if need be.
comment:6 Changed 9 years ago by Veence (Vincent)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I suppose it has been corrected since. Closing this ticket.
The postgis2 build log file ...