I believe if you set the GRASS_WISH environment variable before
starting GRASS that could get around this for you.
E.g.:
export GRASS_WISH=wish8.4 (then start GRASS)
However, it also suggests that a link between wish8.4 and wish is
missing on your system. On my linux and macosx systems, /usr/bin/
wish is a symbolic link to /usr/bin/wish8.4
You could make the same thing with
sudo ln -s /usr/bin/wish8.4 /usr/bin/wish
(that's assuming your wish8.4 is in /usr/bin).
On 30-May-07, at 07:44 , Juan Diego Giraldo Osorio wrote:
Agustin
I started grass with
[EMAIL PROTECTED] ~]$ grass62
and the prompt shows
GRASS 6.2.1 (SENEGAL):~ >
I'm working in a Mapset called SENEGAL.
From here I access to r.example's directory:
GRASS 6.2.1 (SENEGAL):~ > cd grass-6.2.1/dist.x86_64-unknown-linux-
gnu/bin
GRASS 6.2.1 (SENEGAL):~/grass-6.2.1/dist.x86_64-unknown-linux-gnu/
bin >
and here I try to execute r.example:
GRASS 6.2.1 (SENEGAL):~/grass-6.2.1/dist.x86_64-unknown-linux-gnu/
bin >
./r.example
sh: wish: command not found
"ERROR"
Again, I think that grass doesn't call the suitable command (wish8.4
instead wish) but I don't know how (or where) redir the code.
Thanks
Juan
Juan,
You need to start grass before, something like ./grass.sh or simply
grass6, and once grass is started , you will see the following
GRASS 6.3.cvs (Projecte):/your path/ >
There is where you need to put r.example
Best
n May 30, 2007, at 1:06 PM, Juan Diego Giraldo Osorio wrote:
Hi coworkers
Now I have compiledand installed the grass-6.2.1 package with the
following instruction:
./configure --with-postgres-includes=/usr/local/pgsql/include
--with-postgres-libs=/usr/local/pgsql/lib --enable-64bit
--with-libs=/usr/lib64
the procedure don't show problems. However, when I try to execute
./r.example in /dist.x86_64-unknown-linux-gnu/bin the prompt shows:
sh: wish: command not found
I have tcl8.4 and tk8.4. when I execute "wish8.4" tk runs without
problems. I think that the problem is the grass isn't executing the
correct command, but I don'k know how to redir to wish8.4 instead
wish.
Thanks
Juan
On Wed, May 30, 2007 at 05:39:19AM +0100, Glynn Clements wrote:
Markus Neteler wrote:
you have to run GRASS commands *inside* GRASS, means, that
you have to launch GRASS first. Then all paths will be
defined.
To start the version of GRASS which has just been compiled,
without
having to install it, run "bin.i486-pc-linux-gnu/grass62".
Hi Juan,
once you have it all working for you - please let us know where
and how to better document it!
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev