[GRASSLIST:1261] Re: Re: Two more grass5b10 gnats

GRASS GRASS user
1

RGK allegedly wrote:

----- Original Message -----
From: Justin Hickey
To: bob@math.umn.edu ; grasslist@baylor.edu
Sent: Wednesday, December 13, 2000 11:34 AM
Subject: [GRASSLIST:1256] Re: Two more grass5b10 gnats

Hi Chris
bob@math.umn.edu wrote:
>
> For your enjoyment ...
>
> Running grass5 died (linux prompt) and was only fixed by editing
> /usr/local/grass5/tcltkgrass/script/gis_set.tcl to comment out lines:
>
> 706 #if { [string compare -nocase $ver "8.0"] < 0} \
> 707 #{
> 708 # puts stderr "Sorry your version of Tcl/Tk is $ver and is too
> old for GRASS."
> 709 # puts stderr "GRASS requires a TCL/TK version of 8.0 or more."
> 710 # puts stderr "Reverting back to text mode interface."
> 711 # exit 1
> 712 #}

Actually, a better fix is to simply delete the -nocase option (and
remove the comments :).

That would assume I had a clue, of course. Thanks, done, and works. :^)
  

> When the GUI pops up, starting the monitor fails because my $PATH is
> too long for it. Running d.mon from the grass5 prompt works fine.
> Perhaps the Tcl/Tk should not worry so much about the size of
> environmental variables. If that is possible ...

Hmmm. I'm not sure what the problem is here, I do not know of any limit
to the size of environment variables. What is the actual error message
you get?

Error: Error: Aborting!
Excessive environmental variable length:
'PATH=/a/very/many/paths/all/strung/together/over/9/lines/in/the/popup'
child process exited
abnormally

Thanks for notifying us of these problems.

You may regret those words, friend. ;^l

<snip>

Thanks for your time.

Adios,
Chris
--
C.S. Cornuelle
School of Mathematics/MCIM, University of Minnesota
206 Church St. SE, Minneapolis, MN 55455
(612) 626-8930v, (612) 624-2333f, bob at math.umn.edu
Ferventer Vestite

2

Hi Chris

bob@math.umn.edu wrote:

Error: Error: Aborting!
Excessive environmental variable length:
'PATH=/a/very/many/paths/all/strung/together/over/9/lines/in/the/popup'
child process exited
abnormally

Hmmm, it seems I can't reproduce your error message. I made a Tcl/Tk
script that set the PATH environment variable to a string of more than
8000 characters and it never complained. And a search for the error
message in the Grass sources indicates the message is not from Grass. My
"guess" is that the error is caused by your shell. At least I have heard
of these errors occurring in shells.

Sorry I can't be of much help. :frowning:

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand

People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!

3

On Thu, Dec 14, 2000 at 02:10:52PM +0700, Justin Hickey wrote:

Hi Chris

bob@math.umn.edu wrote:
> Error: Error: Aborting!
> Excessive environmental variable length:
> 'PATH=/a/very/many/paths/all/strung/together/over/9/lines/in/the/popup'
> child process exited
> abnormally

Hmmm, it seems I can't reproduce your error message. I made a Tcl/Tk
script that set the PATH environment variable to a string of more than
8000 characters and it never complained. And a search for the error
message in the Grass sources indicates the message is not from Grass. My
"guess" is that the error is caused by your shell. At least I have heard
of these errors occurring in shells.

Sorry I can't be of much help. :frowning:

A PATH length restriction is probably a function of the shell/OS. Some
may place an arbitrary limit of 1024 characters for instance. The only
solution I can think of is to reduce the number of entries for your
system PATH settings. Tools like stow can be used to manage software
installed in /usr/local for instance, removing the necessity to have a
bunch of extra PATH values when each package is installed in it's own
directory (it uses a bunch of symlinks to put executables, libes, etc in
common paths like /usr/local/bin, /usr/local/lib, etc.).

--
Eric G. Miller <egm2@jps.net>