Just loaded grass4.1 and Xgrass4.1
grass4.1 seems to run ok.
xgrass4.1 is giving me problems. It starts, I define mapsets, it
enters the main menu fine, after that no grass commands will execute,
including the SHELL option on the menu.
Whenever the menu "executes" a grass command, I get one of the following
error messages, and the command does not execute:
ETMP = (null)
bad address
OR
STMP = (null)
bad address
Any ideas or suggestions???
Thanks in advance.
John
___________________________________________________________________
U.S. Army Corps of Engineers
JOHN DEL FERRO Philadelphia District
tel: 215-656-6690
johnd@nap61.nap-wc.usace.army.mil
___________________________________________________________________
johnd@nap61.nap-wc.usace.army.mil (John Del Ferro) writes:
:
:
: Just loaded grass4.1 and Xgrass4.1
:
: grass4.1 seems to run ok.
:
: xgrass4.1 is giving me problems. It starts, I define mapsets, it
: enters the main menu fine, after that no grass commands will execute,
: including the SHELL option on the menu.
:
: Whenever the menu "executes" a grass command, I get one of the following
: error messages, and the command does not execute:
:
: ETMP = (null)
: bad address
:
: OR
:
: STMP = (null)
: bad address
:
:
: Any ideas or suggestions???
:
I had a similar problem and got a bug fix from Randy Hills which worked fine:
(From rhills@snow.nohrsc.nws.gov (Randy Hills)):
The following is a bug fix for xgrass in xc.name.c that I've had to apply
in the RS6000 environment in order to get text strings in menus to be
readable. My feeling is the fix is applicable to other environments, the
ifdef was put there to retain the original code. The following is a diff of
the old and new routines:
% diff xc.name.c.orig xc.name.c
259a260,262
> #ifdef _AIX
> static char retBuf[256];
> #else
260a264
> #endif
--
Haefele Georg
haefele@atlas.gis.univie.ac.at
Geography, University of Vienna