Mark Cave-Ayland wrote:
Actually the original poster is right, and the message is not particularly clear. Let me see about changing it...
Hmmm I think the original poster has misquoted the message. According to SVN, if geos-config can't be found in the current path then the error message output will be:
"could not find geos-config within the current path. You may need to try re-running configure with a --with-geosconfig parameter."
If a "--with-geosconfig" parameter is specified on its own without a path then the error message output will be:
"you must specify a parameter to --with-geosconfig, e.g. --with-geosconfig=/path/to/geos-config"
And finally, if you pass a filename that doesn't exist then you get: "the user-specified geos-config file $GEOSCONFIG does not exist" All of this looks reasonably clear to me... ATB, Mark. -- Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS Sirius Corporation plc - control through freedom http://www.siriusit.co.uk t: +44 870 608 0063 Sirius Labs: http://www.siriusit.co.uk/labs _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
