Hey folks!
I was trying to get XGRASS v4.2.1. running on my Solaris v2.6 box when I
ran into a few problems...first, I noticed that XGrass was making a call
to "/lib/cpp" which doesn't exist on my system and afterward, quickly
crashed with a core dump. I corrected this (changed it to
/usr/ccs/lib/cpp) and rebuilt the executables and tried again, only to
get the same core dump, gdb reports the program stack as:
(gdb) backtrace
#0 0xef634170 in _XmManagerInstallMnemonic (m=0x85958, w=0x9fea8,
mn=70)
at Manager.c:1967
#1 0xef612ff8 in initialize (request=0xefffd898, new_w=0x9fea8,
args=0xefffd7c0, num_args=0xefffd74c) at Label.c:716
#2 0xef5268f4 in CallInitialize ()
#3 0xef526898 in CallInitialize ()
#4 0xef526f58 in xtCreate ()
#5 0xef5274c4 in _XtCreateWidget ()
#6 0xef559af4 in _XtVaCreateWidget ()
#7 0xef559ca8 in XtVaCreateManagedWidget ()
#8 0x1bfa8 in __XgHistorySetup ()
#9 0x1a3c0 in main ()
I was curious if there is a relation between the coredump, the call to
"cpp" and one of the above routines. I'll be peeking in the code to see
if I can get an inkling as to what's going wrong on this end, but XGRASS
is a huge and
daunting program, even with the source available.
So before I start examining every line with a fine tooth comb...has
anyone gotten XGrass to work on a Sun UltraSPARC running Solaris v2.6?
That way at least I'll have some inkling as to how serious the problem
is.
Thanks.
--
Clifton B. Wood
Programmer/Analyst for Virginia Tech's AGNIS Department
-------------------- Thought of the Day --------------------
windows95 = n. 32 bit extensions and a graphical shell for
a 16 bit patch to an 8 bit operating system originally coded
for a 4 bit microprocessor, written by a 2 bit company that
can't stand 1 bit of competition.
Hey again!
So before I start examining every line with a fine tooth comb...has
anyone gotten XGrass to work on a Sun UltraSPARC running Solaris v2.6?
That way at least I'll have some inkling as to how serious the problem
is.
After mucking about with the sources some more, I decided to upgrade the
installed copy of LessTIF with the one provided in the 4.2.1 release and
then recompiled the actual xgrass EXE. It runs now and pops up a window,
but when it prompts me for a database, I only see the first part, (the
path where the locations are stored - GISBASE) I don't see any
of our installed locations or mapsets. How do I set this up under
XGrass? Or is there still something wrong with the executable that's
preventing these choices from appearing?
Thanks.
- Cliff
--
Clifton B. Wood
Programmer/Analyst for Virginia Tech's AGNIS Department
-------------------- Thought of the Day --------------------
windows95 = n. 32 bit extensions and a graphical shell for
a 16 bit patch to an 8 bit operating system originally coded
for a 4 bit microprocessor, written by a 2 bit company that
can't stand 1 bit of competition.
CW> After mucking about with the sources some more, I decided to
CW> upgrade the installed copy of LessTIF with the one provided in the
CW> 4.2.1 release and then recompiled the actual xgrass EXE. It runs
CW> now and pops up a window, but when it prompts me for a database, I
CW> only see the first part, (the path where the locations are stored
CW> - GISBASE) I don't see any of our installed locations or
CW> mapsets. How do I set this up under XGrass? Or is there still
CW> something wrong with the executable that's preventing these
CW> choices from appearing?
I dont have Xgrass on my home computer, but at work i compiled grass
under Linux with the version of Lesstif provided by grass. First I
have the same behavior than you discribe, I can pass this step by
passing parameters in command line argument to xgrass (try xgrass
--help or something like this) for location mapset and database.
like xgrass -location=leics -mapset=dreau
-database=/usr/local/grass42/data
CW> - Cliff --
My 2 eurocents
--
Hervé Dréau Interne en Médecine
hdreau@worldnet.fr dreau@b3e.jussieu.fr
Médecine Linux Java
Herve Dreau wrote:
I dont have Xgrass on my home computer, but at work i compiled grass
under Linux with the version of Lesstif provided by grass. First I
have the same behavior than you discribe, I can pass this step by
passing parameters in command line argument to xgrass (try xgrass
--help or something like this) for location mapset and database.
like xgrass -location=leics -mapset=dreau
-database=/usr/local/grass42/data
Aha!
Now why didn't I think of that? :>
I'll still be mucking with the code to see why the other 2 selection
boxes
don't work when I get some time. I find it counter intuitive to have to
use COMMAND LINE options to do something the interface should use, but
this
works right now as a quick fix!
My 2 eurocents
A cent saved is a cent earned. Thanks much!
============================================================
Clifton B. Wood
Programmer/Analyst for Virginia Tech's AGNIS Department
-------------------- Thought of the Day --------------------
windows95 = n. 32 bit extensions and a graphical shell for
a 16 bit patch to an 8 bit operating system originally coded
for a 4 bit microprocessor, written by a 2 bit company that
can't stand 1 bit of competition.