Thanks for the help:
Maris Nartiss wrote: > > env | grep GISBASE > It should give something like: > GISBASE=/path/to/grass-6.4 > GISBASE=/usr/lib/grass64/ contentes of /usr/bin/grass64: [...] # Set the GISBASE variable GISBASE=/usr/lib/grass64 export GISBASE exec "$GISBASE/etc/Init.sh" "$@" If in a grass shell I cd to /usr/lib/grass64/bin (which contains g.gisenv) all is well (obviously). If I set PATH to contain "/usr/lib/grass64/bin" no errors are reported, even if leave the directory /usr/lib/grass64/bin. If I set PATH to contain "/usr/lib/grass64/" the errors are reported again. Should I set GISBASE to /usr/lib/grass64/bin in /usr/bin/grass64, or will that make problems? And the more general question is: how can I repair my broken install? Is an aptitude reinstall enough to correct things? Thanks for the help, Ed. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/debian-lenny-usr-lib-grass64-etc-prompt-sh-line-2-g-gisenv-command-not-found-tp5230349p5234144.html Sent from the Grass - Users mailing list archive at Nabble.com. _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
