Code

Changes between Version 20 and Version 21 of GeoDjangoInstall


Ignore:
Timestamp:
10/01/07 09:43:23 (7 years ago)
Author:
ariel
Comment:

Added more information about library errors and debugging.

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjangoInstall

    v20 v21  
    8282}}} 
    8383 
    84  * 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`). On Solaris platforms use the `crle` utility to configure the runtime linking environment. 
     84 * 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. 
    8585 
    8686 * Finally, update your {{{settings.py}}} to reflect the name and user for the spatially enabled database.  So far, we only plan to support the psycopg2 backend, thus: {{{DATABASE_ENGINE='postgresql_psycopg2'}}}.