A.22 Why won't TCM start saying ``libBlaBla.so: can't open file''?

   

This is due to to the fact that the system cannot find a shared library needed by TCM. When you execute the command ldd `which tcm`, you see against which libraries TCM is linked and where these are found (if they are found) on your system. The remedy to this problem depends on the kind of BlaBla.

• If BlaBla is either libglobal.so, libgui.so, libeditor.so, libdiagram.so or libtable.so then TCM cannot find its own libraries. Check if they are installed in $TCM_HOME/lib. If they are, set your LD_LIBRARY_PATH variable to $LD_LIBRARY_PATH:$TCM_HOME/lib.  
• If BlaBla is libXm.so then TCM cannot find the Motif library. Look in the README.TCM of the TCM distribution where it should reside. Check also the version number of the Motif library. As it is impossible to run with version 1.2 when it needs 2.0 and vice versa. When you do not have Motif, you should obtain a distribution in which Motif is statically linked (see question A.9). If you have Motif, you could try to set the LD_LIBRARY_PATH to include the Motif library directory.

  In the past, the Linux executables of TCM were stripped too rigorously so that a Motif library with a different minor revision number than the one we used, could not be dynamically linked. Hopefully the current version of TCM has fixed this problem.

• If BlaBla is libX11.so, libXt.so or something else with an X in it, then TCM cannot find one of the X Windows libraries. Look in the README.TCM where TCM expects them to reside and look where they actually are on your system. Install them in the expected directory, or append to your LD_LIBRARY_PATH the directory where they actually are.
• If BlaBla is something else, like for instance libC.so.5 or libg++.so.27 then some other Unix or C library cannot be found. Either set your LD_LIBRARY_PATH, if they are at a different place than expected or install them if that is possible.

If you are still in big need, you can always try to ask us for help or for the library that you need (provided that this is allowed) or maybe it is possible to build a distribution in which that library is statically linked.