Hello,
Yes, that is almost certainly the problem. We have had problems like this
with Tcl/Tk on other Linux installations. Indeed, on one system we told
it to pick up a specific Tcl/Tk and insisted instead on using one in
/usr/local and the only way we got around that one was to delete the
/usr/local version (fortunately they didn't need it). So just downloading
and compiling the version of Tcl/Tk from the CCPN website might not help.
If you start python and do the following:
> python
>>> import Tkinter
>>> r = Tkinter.Tk()
and then do lsof on that, you will see what Tcl/Tk python is picking up.
And then I would use the same version of Tcl/Tk in environment.txt.
Hopefully that will sort things out. Analysis should run with either
Tcl/Tk 8.3 or 8.4 (You might also need to set TCL_LIBRARY and TK_LIBRARY,
not sure about that for Ubuntu. If when running Analysis you still get a
mixed Tcl/Tk we can worry about these environment variables next.)
The bad news is that in (probably) the next release of Analysis we are
moving up to Python 2.4. (We want to use sets, and although 2.3 has them
it doesn't have them in the same way.) So one more thing to add to the
pot.
Wayne
On Sat, 27 Jan 2007, Mark Girvin wrote:
> Wayne, thanks for the reply!
>
> And for the "lsof" suggestion - the results involving tcl/tk/gl were:
>
> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
> python 1874 girvin txt REG 8,3 983480 618984 usr/bin/python2.3
> python 1874 girvin mem REG 8,3 952432 263680
> /usr/lib/libBLT.2.4.so.8.4
> python 1874 girvin mem REG 8,3 886224 263676
> /usr/lib/libtk8.4.so.0
> python 1874 girvin mem REG 8,3 713832 263674
> /usr/lib/libtcl8.4.so.0
> python 1874 girvin mem REG 8,3 175104 263835
> /usr/lib/libglut.so.3.8.0
> python 1874 girvin mem REG 8,3 733968 264196
> /usr/lib/libtk8.3.so.1
> python 1874 girvin mem REG 8,3 500608 587077
> /usr/X11R6/lib/libGLU.so.1.3
> python 1874 girvin mem REG 8,3 437376 587074
> /usr/X11R6/lib/libGL.so.1.2
> python 1874 girvin mem REG 8,3 525232 264189
> /usr/lib/libtcl8.3.so.1
>
> I'm using the standard debian distribution packages, so don't know which
> mix of versions was used in compiling python. But seeing both libtk8.4
> and libtk8.3 in the above output doesn't look good. Would it be best to
> just download the separate python / tcl / mesa packages from ccpnmr
> and build and use those w/in the ccpnmr directory? (it's getting a
> little busy with multiple programs wanting or needing to use private
> copies of python, tcl, tk, etc, but maybe there's no good way around
> it).
>
>
> Again, thanks, - Mark
>
>
> On Sat, Jan 27, 2007 at 01:22:45AM +0000, Wayne Boucher wrote:
> > Hello,
> >
> > A couple of quick questions. Are you using Tk graphics (definitely yes if
> > you didn't install the OpenGL)? And was the Python you are using compiled
> > against the same Tcl/Tk that was used to compiled Analysis (otherwise all
> > hell would break loose). And if you are using OpenGL, the same questions
> > go for the GL and glut libraries and Analysis. (On some Linux systems you
> > can type "lsof -p" to see what libraries have been loaded for a given
> > process.)
> >
> > Wayne
> >
> > PS: Another Ubuntu user had similar problems with the installation script.
> > It turns out the Tcl/Tk stuff is ordered differently (i.e. is in different
> > directories) than in all our previously known systems. I'll have to
> > extend the script to deal with this situation.
>
|