Top Up Prev Next Bottom Contents Index Search

G.1 Problems starting pigi

Mr. Ptolemy window does not come up

Ptolemy consists of two processes, vem and pigiRpc, that communicate via Remote Procedure Calls (RPC). Vem is the first process that starts up, and it produces a vem console window in the upper left corner of the screen and a green demo window just below it. When pigiRpc starts up, you should see a window in the middle of your screen that has the Mr. Ptolemy bitmap and a brief description of the binary you are running.

If the pigiRpc process fails to connect to the vem process, you won't see the Mr. Ptolemy bitmap, and the shift-middle-button menus will not be active. This problem seems to be most common on Linux machines, in part because they are often not on a network. If you are running under Linux and your installation is configured to use the network, then you may need to rebuild Ptolemy from source.

If you are running on a machine that is not connected to a network, you will need to provide some network support for pigi to start up. vem and pigiRpc communicate with each other via RPCs, which require some intra-machine network support. One quick test is that you should be able to ping yourself:

/usr/etc/ping `hostname`

There are several workarounds to this. One is to add the name of your host to the loop back line in /etc/hosts (here we add the name myhostname): localhost myhostname Another solution is to use route to route packets to your host through the loopback interface. As root, type:

route add `hostname` localhost 0 See the ping, netstat and route commands for more information.

pigi fails to start when put in the background

A common problem occurs when pigi is started in the background and the user has the line

stty tostop in their .login or .cshrc file. This command configures the terminal to halt any process that is running in the background when it tries to write to the terminal. One fix is to run pigi in the foreground. Another fix is to eliminate this command from your login files.

pigi fails to start up, giving shared library messages

On certain platforms, Ptolemy is built using shared libraries. In Ptolemy 0.6, the Solaris, HP and possibly Linux platforms use shared libraries. See the "Shared Library" appendix for more information about shared libraries.

At run time, if shared libraries cannot be found, you may see a message under HPUX-10.01 like:

/usr/lib/ Can't find path for shared library: Under Solaris 2.x, you might see: /users/cxh/pt/bin.sol2/vem: fatal: can't open file: errno=2 The message that you see may vary but the problem is that the binary cannot find the shared libraries to which it was linked. There are a few reasons this could be happening:

setenv SHLIB_PATH {$PTOLEMY}/lib.{$PTARCH}:\ {$PTOLEMY}/octtools/lib.{$PTARCH}:{$PTOLEMY}/gnu/{$PTARCH}/lib For Solaris, you could type the following command (all on one line):

setenv LD_LIBRARY_PATH {$PTOLEMY}/lib.{$PTARCH}:\ {$PTOLEMY}/octtools/lib.{$PTARCH}:{$PTOLEMY}/gnu/{$PTARCH}/lib It is best to place these commands in your ~/.cshrc file. It is possible that you might have to add other directories to the shared library path. For example, the Ptolemy binaries are compiled with /usr/openwin/lib as the location of the X windows libraries. If your X windows libraries are in another directory, then you will need to add that directory to the shared library path. See "Window system problems" on page 7-182.

tycho fails to start up, giving TCL_LIBRARY messages

There are several ways to start up tycho, the Ptolemy syntax manager. $PTOLEMY/bin/tycho is a link to a script that processes command line arguments and starts up the appropriate binary. If you type tycho -pigi, tycho starts up with a binary that includes the Ptolemy system. If you type just tycho, then tycho starts up with the generic itkwish binary that is built from the itcl sources, which does not include any of the Ptolemy system.

If your Ptolemy distribution is not at /users/ptolemy, and you are running from prebuilt binaries, then if you run tycho with the prebuilt generic itkwish binary, you may see messages about:

application-specific initialization failed: can't find /users/ptolemy/tcltk/itcl/lib/tcl7.4/init.tcl; perhaps you need to install Tcl or set your TCL_LIBRARY environment variable? What's happening here is the itkwish binary we ship has the /users/ptolemy path hard coded into it and the binary is not finding the libraries it needs. The reason this happens is that we want tycho to be able to run outside of Ptolemy on machines that have only generic itkwish installed from the itcl distribution. There are a few workarounds:

exec $PTOLEMY/bin/tycho $*

Top Up Prev Next Bottom Contents Index Search
Copyright © 1990-1997, University of California. All rights reserved.