please add --with-topology to the configure. Topology is an important and new feature coming in PostGis 2.0
Search Criteria
Package Details: postgis-svn 6280-2
Package Actions
- View PKGBUILD
- Download tarball
- Search wiki
- Flagged out-of-date (2014-12-24)
| Package Base: | postgis-svn |
|---|---|
| Description: | Adds support for geographic objects to PostgreSQL; including the experimental PostGis RASTER type. |
| Upstream URL: | http://trac.osgeo.org/postgis/ |
| Category: | science |
| Licenses: | |
| Submitter: | None |
| Maintainer: | None |
| Last Packager: | None |
| Votes: | 1 |
| First Submitted: | 2010-04-25 17:24 |
| Last Updated: | 2010-12-06 15:20 |
Latest Comments
Comment by andrea76
Comment by bnordgren
Note that as of the upstream's r7781, the following line in the PKGBUILD is no longer necessary and must be removed:
sed 's:$(PGSQL_BINDIR):$(DESTDIR)/$(PGSQL_BINDIR):g' -i ${srcdir}/trunk-build/raster/scripts/python/Makefile.in
Comment by bnordgren
Upstream bug report: http://trac.osgeo.org/postgis/ticket/970
Comment by bnordgren
postgis (with raster support) does not compile on arch anymore. The configure script hardcodes "python" as the python executable. This is python 3 on Arch, and GDAL installs its python bindings into the python 2 installation. In essense, postgis looks for gdal python bindings in python 3 instead of python2.
I modified this PKGBUILD to make the ./configure pay attention to the python environment variable. Then it sets PYTHON=python2 on the "configure" and "make" command lines. This is a hack, but it seems to work. The real solution will come when the upstream allows you to specify the python executable.
Modified pkgbuild: http://pastebin.com/yAjxFV0S