Could someone familar with python give sparky a test on debian
i386 sid? On debian ppc sid the program segfaults on loading its
python module. The source for the program is available from...
http://www.cgl.ucsf.edu/home/sparky/
as sparky-source-3.106.tar.gz. If you untar it in /usr/local/src
a
Could the maintainer please fix this or someone NMU it? The fix
is absolutely trivial if you use the new Pmw.1.1.tar.gz from
http://download.sourceforge.net/pmw/. In fact a complete diff sans
changelog changes is attached and will work perfectly when...
tar -zxvf Pmw.1.1.tar.gz
mv Pmw.1.1 pyth
Actually on second thought we better stick with the current
python-pmw_0.8.5-6 adjusted to build against python 2.2. Things
like pymol are having issues running with pmw 1.1. The patches
required to get python-pmw_0.8.5-6 built with python 2.2 are
attached below... Thanks in advance.
Michael,
Could you change that NMU to a Pmw 1.1 release please? The Pmw
developer just gave me a fix for pymol (it was misusing a call which
is now marked as an error message in 1.1). So we really should have
no reason now not to migrate forward to Pmw 1.1. Thanks.
Could someone familar with python give sparky a test on debian
i386 sid? On debian ppc sid the program segfaults on loading its
python module. The source for the program is available from...
http://www.cgl.ucsf.edu/home/sparky/
as sparky-source-3.106.tar.gz. If you untar it in /usr/local/src
a
Sorry about the duplicate message. I get a bounce back from the
list server that seemed to indicate the first message was rejected
as spam because of the title. So I resent it with a modified title.
Jack
I believe I may have a clue as to why sparky is segfaulting in
when run as a python extension. The upstream maintainer is using
python 2.1.1 and tcl 8.3.4 so I built against our python 2.1.3 and
tck 8.3.3. However I just noticed that sid's python2.1 is in
fact built against tcl-8.4 now. Could t
Emil,
Actually it is probably something else. I had a user with YellowDog
Linux 2.3 try sparky against python 2.1.1 and tcl 8.3.3 and he segfaults
as well. Are you on i386 or ppc debian? If i386, I would be very interested
if sparky segfaults on that arch as well. It has been built on redhat
lin
Just in case anyone is interested, I have resolved the problems
of building a usable python version of sparky with debian ppc sid by
patching it to build under gcc 3.2.2. Interestingly the gcc 2.95.4
build segfaults but a gcc 3.2.2 build works fine. Since sparky uses
its own __tkinter.so with t
9 matches
Mail list logo
