Opened 13 years ago
Closed 13 years ago
#1575 closed defect (fixed)
Configured without raster still tries to make raster/rt_pg/rtpostgis.sql
Reported by: | chmelarp | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.0 |
Component: | build | Version: | 2.0.x |
Keywords: | Cc: |
Description
Hi,
after:
$ ./configure --without-topology --without-raster && make
I get these ...
/usr/bin/xsltproc ./xsl/raster_comments.sql.xsl postgis.xml > raster_comments.sql
/usr/bin/xsltproc ./xsl/topology_comments.sql.xsl postgis.xml > topology_comments.sql
/usr/bin/xsltproc ./xsl/tiger_geocoder_comments.sql.xsl postgis.xml > tiger_geocoder_comments.sql
make[3]: Leaving directory `postgis-2.0.0alpha5SVN/doc'
cp ../../doc/postgis_comments.sql sql_bits/postgis_comments.sql
make[2]: * No rule to make target ../../raster/rt_pg/rtpostgis.sql', needed by
sql_bits/rtpostgis.sql'. Stop.
make[2]: Leaving directory `postgis-2.0.0alpha5SVN/extensions/postgis'
Change History (2)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Only building extensions if we have raster, topology, pgsql9.1+ at r9182
The issue it looks like is that its trying to make the extensions probably becasue running 9.1.
I think the best thing to do is to not allow building extensions if raster and topology are disabled.
We can't have two versions of postgis extensions one with raster and one without because its really not the same extension.
If just topology is disabled I suppose we can disable the topology extension building.
Paul -- can you make this change. Not sure how to since I don't know how it plays with the whole configure script.