[GRASS5] Re: Terminal Errors

On: Mon, 19 Feb 2001, John Huddleston wrote:

Subject: Re: [GRASS5] vt100 error with osx + xterm error

Justin,

I get that same message using Cygwin. I checked the
/usr/lib/terminfo and all is well there. I'll look at the
initscr

John Huddleston

And on: Mon, 19 Feb 2001, John Huddleston wrote:

Subject: Re: [GRASS5] vt100 error with osx + xterm error

Well, I fixed the error for Cygwin. It turned out that the
/usr/lib/terminfo directory was a symbolic link to the
./share/terminfo directory. I removed the symbolic
link, moved the share terminfo directory to /usr/lib and
created a symbolic link from share to ../lib for the
terminfo directory. No more error message. That's
a weird one. It might be because I am using the X-win32
server from StarNET. Programs compiled outside of
Cygwin do not recognize the Cygwin symbolic links. The
xfree binary should work OK.

John Huddleston

Hi,

I just looked, and I do not have a /usr/lib/terminfo, in fact there is not a terminfo anywhere on my system. Could that be the problem? How might I create such a file?

Thanks,

Jeshua Lacock
Cartographer/Owner
http://SierraMaps.com
http://3dTopoMaps.com
Telephone: (760) 935-4481

---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Jeshua Lacock wrote:

I just looked, and I do not have a /usr/lib/terminfo, in fact there is
not a terminfo anywhere on my system. Could that be the problem? How
might I create such a file?

"terminfo" is a directory, containing lots of one-character
subdirectories, each containing one file per terminal. E.g. the file
for "xterm" would be .../terminfo/x/xterm. The files are created with
"tic".

Looking back at Andy's emails, it seems that the curses library
supplied with MacOS X doesn't use terminfo, but instead uses the older
"termcap" file (typically /etc/termcap, although an email from Andy
suggests that it is /usr/share/misc/termcap). Also, it appears that
the relevant environment variables may be set incorrectly.

Try setting TERMCAP and/or TERMPATH to /usr/share/misc/termcap, e.g.

  TERMCAP=/usr/share/misc/termcap
  export TERMCAP

for Bourne shell or

  setenv TERMCAP /usr/share/misc/termcap

for C shell.

--
Glynn Clements <glynn.clements@virgin.net>

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Hi Jeshua:

I never figured this out (a small piece of Glynn's suggestions for me are pasted below). I have a feeling this goes back to some change in the dynamic libraries problem I encountered with the CVS version. I suspect that there was some change in OS X between the the public beta and 10.0.x (I'm using 10.0.3).

However, this might be a start for you:

[localhost:/usr/share/misc] root# ls
  termcap termcap.db [et al.]
[localhost:/usr/share/misc] root# $TERMCAP
d0|vt100|vt100-am|vt100am|dec: No match.
[localhost:/usr/share/misc] root# $TERMPATH
TERMPATH: Undefined variable.
[localhost:/usr/share/misc] root#

Andy

<snip>

I just looked, and I do not have a /usr/lib/terminfo, in fact there is not a terminfo anywhere on my system. Could that be the problem? How might I create such a file?

[from correspondence with Glynn:]

i found the following (this was in libSystem.B.dylib):

TERMCAP
TERMPATH
HOME
.termcap /usr/share/misc/termcap

so i:

[localhost:/usr/share/misc] andya% $TERMCAP
d0|vt100|vt100-am|vt100am|dec: No match.

TERMCAP is set to "d0|vt100|vt100-am|vt100am|dec"? That isn't right.
It should be either the path to the termcap file, or a termcap-format
entry which describes the terminal; see below.

[localhost:/usr/share/misc] andya% $TERMPATH
TERMPATH: Undefined variable.
[localhost:/usr/share/misc] andya% ls
termcap termcap.db [among others]

"termcap" should be a plain text file, listing all of the different
terminals. termcap.db is presumably a compiled version, but I don't
know what would be used to compile it (GNU ncurses doesn't use a
compiled termcap).

do you think i need to [somehow] define TERMPATH? or, do you want me to
forward termcap and termcap.db to you so you can take a look?

It might suffice to set TERMCAP, e.g.

  setenv TERMCAP /usr/share/misc/termcap

---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Im tryng to compile grass on a Solaris: i encountered 2 problems:

1) "ar" was not in the path, but configure did not complained and
compilation of course failed at src/libes/gis nothing important,
but it could confuse the clueless.

2) It seems to compile and install ok, but grass5 does not start
because of some libz problem. I will investigate further and report,
unless someone already encountered the problem and can tell me.

BTW i didn't expected the grass shell not to start because of libz
problems, as far as i knows only some raster modules needs it...

Federico

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

On Thursday, May 17, 2001, at 06:45 PM, Glynn Clements wrote:

Try setting TERMCAP and/or TERMPATH to /usr/share/misc/termcap, e.g.

  TERMCAP=/usr/share/misc/termcap
  export TERMCAP

for Bourne shell or

  setenv TERMCAP /usr/share/misc/termcap

for C shell.

Thanks Glynn,

I tried your suggestions to no avail.

Note that within the X-Windows environment if I type "xterm", it launches a new terminal window. If I am in the Mac OS X "Aqua" environment and type "vt100", it says command not found.

It seems to me that there is a tricky yet simple reason behind this whole terminal problem.

Any other suggestions? Would you like to see my "env"? My (default) TERMCAP environment variable is about two hundred weird characters.

Thanks again,

Jeshua Lacock
Cartographer/Owner
http://SierraMaps.com
http://3dTopoMaps.com
Telephone: (760) 935-4481

---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Jeshua Lacock wrote:

Note that within the X-Windows environment if I type "xterm", it
launches a new terminal window. If I am in the Mac OS X "Aqua"
environment and type "vt100", it says command not found.

Most terminal names do not correspond to a command; "xterm" is the
exception.

It seems to me that there is a tricky yet simple reason behind this
whole terminal problem.

Yep; MacOS X has a broken curses installation. Are there any mailing
lists, web sites etc specifically for MacOS X issues? If there are,
they would probably be of more help than this list. This problem is
unlikely to be specific to GRASS; any program which tries to use
curses should suffer from the same problems.

Any other suggestions? Would you like to see my "env"? My (default)
TERMCAP environment variable is about two hundred weird characters.

I'm not sure that would help. It's legal for $TERMCAP to be an actual
termcap entry rather than the path to the termcap file. However, in
this case, curses should be ignoring $TERM.

--
Glynn Clements <glynn.clements@virgin.net>

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Federico Ponchio wrote:

2) It seems to compile and install ok, but grass5 does not start
because of some libz problem. I will investigate further and report,
unless someone already encountered the problem and can tell me.

BTW i didn't expected the grass shell not to start because of libz
problems, as far as i knows only some raster modules needs it...

No, etc/set_data (the program which interactively prompts for
location, mapset and database) is linked against libz, as is anything
which has $(XDRLIB) in the link command.

--
Glynn Clements <glynn.clements@virgin.net>

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Glynn and Jeshua:

Yep; MacOS X has a broken curses installation. Are there any mailing
lists, web sites etc specifically for MacOS X issues? If there are,
they would probably be of more help than this list. This problem is
unlikely to be specific to GRASS; any program which tries to use
curses should suffer from the same problems.

The darwin list at apple is probably the best for this question:

http://www.lists.apple.com/mailman/listinfo/darwin-development

But there's also the developer list at omni:

http://www.omnigroup.com/mailman/listinfo/macosx-dev

Andy

---------------------------------------- If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

Hi Frederico,

what a coincidence. I just finished a compile on Solaris 2.7 SPARC right
now.

For your problems:
You should install either the GNU binutils package, which contains IMHO
the library archiver, or create a softlink from /usr/xpg4/bin/ar to
/usr/bin/ar or add /usr/xpg4/bin to your search path.

For the library problems: You will encounter the same problem with other
libraries too (e. g. libtiff, libpng etc.).
You can add /usr/local/lib (where GNU libz is installed by default) to
your LD_LIBRARY_PATH or you may create links to all needed libraries in
/usr/lib. Perhaps some seasoned solaris people can tell us if one can
add the /usr/local/lib directory to a system wide library search path. I
don't know right now.

There are some additional problems with scripts starting with
#!/bin/bash ( i will take care of this ) and g.manual not working
correctly. More on this later.

cu,

Andreas

Federico Ponchio wrote:

Im tryng to compile grass on a Solaris: i encountered 2 problems:

1) "ar" was not in the path, but configure did not complained and
compilation of course failed at src/libes/gis nothing important,
but it could confuse the clueless.

2) It seems to compile and install ok, but grass5 does not start
because of some libz problem. I will investigate further and report,
unless someone already encountered the problem and can tell me.

BTW i didn't expected the grass shell not to start because of libz
problems, as far as i knows only some raster modules needs it...

Federico

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

On Friday, May 18, 2001, at 02:12 AM, Glynn Clements wrote:

It seems to me that there is a tricky yet simple reason behind this
whole terminal problem.

Yep; MacOS X has a broken curses installation. Are there any mailing
lists, web sites etc specifically for MacOS X issues? If there are,
they would probably be of more help than this list. This problem is
unlikely to be specific to GRASS; any program which tries to use
curses should suffer from the same problems.

Any other suggestions? Would you like to see my "env"? My (default)
TERMCAP environment variable is about two hundred weird characters.

I'm not sure that would help. It's legal for $TERMCAP to be an actual
termcap entry rather than the path to the termcap file. However, in
this case, curses should be ignoring $TERM.

All right!!!

Thanks Glynn, and everyone, we finally got this one nailed. I installed ncurses 5.2 and harmony has been restored to the Mac OS X GIS universe.

You no longer have to type location to start grass and modules that were broken now work.

Now to compile pre1....

Markus: Shall I upload a tarball with instructions?

Cheers,

Jeshua Lacock
Cartographer/Owner
http://SierraMaps.com
http://3dTopoMaps.com
Telephone: (760) 935-4481