Jose Miguel Martins Delgado wrote: > 5. A way of dealing with this is to start GRASS directly on a dummy > location, like spearfish60. Then changing the location with g.proj -c. > The problem is that, again, GRASS replies: > > GRASS 6.3.0 > g.proj -c epsg=4326 location=LatLong > g.proj: error while loading shared libraries: libproj.so.0: cannot open > shared object file: No such file or directory
This is probably the reason why the normal location creation process isn't working either. The interactive startup involves invoking various helper programs, e.g. g.setproj to set ellipsoid, datum, etc. If the proj library cannot be found, g.setproj won't work (nor will several other important programs, e.g. g.region). If the proj library isn't installed on the cluster, GRASS isn't going to work. If it's installed, but it's the wrong version, you may need to re-compile GRASS (or it may suffice to create a symlink with the correct name). If the problem is just that GRASS can't find it, setting LD_LIBRARY_PATH may help. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
