Changes between Version 60 and Version 61 of GeoDjangoInstall

Timestamp:

Aug 18, 2008, 4:03:49 PM (16 years ago)

Author:

springmeyer

Comment:

Adding more info about GEOS .so in PostGIS section

GeoDjangoInstall

@@ -167 +167 @@
 $ psql -d <db_name> -f /usr/share/lwpostgis.sql # another possible installation location
 # Note: ignore any NOTICES, like 'psql:/usr/share/lwpostgis.sql:44: NOTICE:  type "histogram2d" is not yet defined'
+# Note: errors like `ERROR:  could NOT access file "$libdir/liblwgeom": No such file OR directory` see troubleshooting below
 }}}
 {{{
@@ -175 +176 @@
 }}}
 
- * Note: if you experience errors about not finding libraries, you may need to adjust your `LD_LIBRARY_PATH` (which may be configured system-wide by editing `/etc/ld.so.conf` and running `ldconfig`)(Hint: Most of the times the libraries you are looking for are in '/usr/local/lib').  Sometimes the errors are too many and not descriptive (i.e. operation aborted), in that cases use the '-s' switch on psql to debug step by step. On Solaris platforms use the `crle` utility to configure the runtime linking environment.
+ * '''Troubleshooting''': if you experience errors about not finding libraries, you should confirm that libgeos.so (.dylib on mac) has been properly installed prior to configuring PostGIS. Otherwise you will need to rebuild PostGIS. If it was built and installed properly you may need to adjust your `LD_LIBRARY_PATH`, or DYLD_LIBRARY_PATH (on mac). (This environment can also be configured system-wide on linux by editing `/etc/ld.so.conf` and running `ldconfig`)
+  * Hint: Most of the times the libraries you are looking for are in '/usr/local/lib', but geos in particular will output its install location during the `make install` step.
+  * Sometimes the errors are too many and not descriptive (i.e. operation aborted), in that cases use the '-s' switch on psql to debug step by step. On Solaris platforms use the `crle` utility to configure the runtime linking environment.
 
 Finally, update your `settings.py` to reflect the name and user for the spatially enabled database (thus far, we only plan to support the `psycopg2` backend for PostgreSQL):