[tkined] Install Scotty 2.1.10 etc. (Digital Unix 4.0D)

Alan J. Flavell (flavell@a5.ph.gla.ac.uk)
Sat, 19 Jun 1999 20:18:06 +0100 (BST)

Greetings; I'm just trying to install Scotty 2.1.10 and friends
on DU 4.0D.

Previous installation had been 2.1.9, this had been done some time
prior to upgrading the OS to 4.0D, and (as far as I recall) went
without problems. That version still executes fine; I just thought it
was time to get a bit more up to date.

With the first attempt at 2.1.10 I got the symptoms discussed in the
thread
http://www.xray.mpe.mpg.de/mailing-lists/tkined/1999-04/msg00064.html

I'm puzzled at the answer given there. Is it really necessary to make
tkined-specific changes in the area of what seems to be standard TCL
stuff?

On the basis of this mail:
http://www.xray.mpe.mpg.de/mailing-lists/tkined/1998-09/msg00054.html
I began to think that perhaps the OS upgrade has installed a version
of TK/TCL that's causing problems, compared with the version of tk/tcl
(8.0.something, installed by me) that was used when Scotty 2.1.9 had
been installed (again, this would have been prior to the OS upgrade).

I went back to my own tk/tcl installation materials, and found version
8.0.4. I tried a re-install of that. At first I noted that it was
installing static libraries, and the scotty notes said it wanted
shared, so I reconfigured the tk/tcl pakage for that. Then I
reinstalled, as I said. By the way, quite a number of the tests in
"make test" in the tcl and tk libraries seem to fail, but this was
pretty much the case before, and I gather it's not fatal.

OK, then back to Scotty, "make distclean", and configured, built and
installed it again. This time, when started by hand, it seems to work
fine.

However, "make check" reports some errors.

==== mib-1.1 mib oid
==== Contents of test case:

mib oid sysDescr

==== Test generated error:
couldn't open MIB file "fms01_40.mib": no such file or directory

This seems to refer to a mib file that I had added manually (and maybe
clumsily?) in an earlier version... (2.1.7), but I can't for the life
of me work out how this version has latched on to it.

The "make check" results continue thus:

==== netdb-3.6 check "netdb services" command
==== Contents of test case:

[...]

==== Result was:
753 != 752

(Is this a knock-on effect from the previous error?).

---- netdb-3.6 FAILED
sh: 8866 Memory fault - core dumped
*** Exit 139
Stop.

Woops?

Any comments on this? It's only very occasionally that I build this
software, and I'm far from being any kind of expert, so all
constructive comments would be welcome.

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.