please help test sparky
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
and then apply the patch below...
----------------------------------------------------------------------
diff -uNr /home/howarth/sparky/c++/Makefile /usr/local/src/sparky/c++/Makefile
--- /home/howarth/sparky/c++/Makefile 2002-01-17 22:14:16.000000000 -0500
+++ /usr/local/src/sparky/c++/Makefile 2002-12-21 13:45:22.000000000 -0500
@@ -17,26 +17,27 @@
SPARKY = /usr/local/src/sparky
SPARKY_SRC = $(SPARKY)/c++
+SPARKY_INSTALL = /usr/local/sparky
PY_VERSION = 2.1
PY_VER = 21
-PYTHON_PREFIX = /usr/local
+PYTHON_PREFIX = /usr
PYTHON_LIB = $(PYTHON_PREFIX)/lib/python$(PY_VERSION)
PYTHON_INC = $(PYTHON_PREFIX)/include/python$(PY_VERSION)
TCLTK_VERSION = 8.3
TCLTK_VER = 83
-TK_PREFIX = /usr/local
+TK_PREFIX = /usr
TK_VERSION = tk$(TCLTK_VERSION)
TCL_VERSION = tcl$(TCLTK_VERSION)
PLATFORM = unix
-CXX = g++
-CXXFLAGS =
-CC = gcc
-CFLAGS =
+CXX = g++-2.95
+CXXFLAGS = -O2 -fPIC
+CC = gcc-2.95
+CFLAGS = -O2 -fPIC
PYFLAGS = -I$(PYTHON_INC) -I$(PYTHON_LIB)/config
-TKFLAGS = -I$(TK_PREFIX)/include
-TKLIBS = -L$(TK_PREFIX)/lib -l$(TK_VERSION) -l$(TCL_VERSION) -lX11
-EXTRALIBS =
+TKFLAGS = -I$(TK_PREFIX)/include/$(TCL_VERSION)
+TKLIBS = -L$(TK_PREFIX)/lib -l$(TK_VERSION) -l$(TCL_VERSION)
+EXTRALIBS = -L/usr/X11R6/lib -lX11
SYSLIBS = -lm
LDLIBS = $(TKLIBS) $(SYSLIBS) $(EXTRALIBS)
LDFLAGS =
diff -uNr /home/howarth/sparky/lib/Makefile /usr/local/src/sparky/lib/Makefile
--- /home/howarth/sparky/lib/Makefile 2002-01-17 22:17:14.000000000 -0500
+++ /usr/local/src/sparky/lib/Makefile 2002-12-20 22:41:32.000000000 -0500
@@ -12,7 +12,7 @@
TCLTK_VERSION = 8.3
TK_VERSION = tk$(TCLTK_VERSION)
TCL_VERSION = tcl$(TCLTK_VERSION)
-TK_PREFIX = /usr/local
+TK_PREFIX = /usr
TCL_TK_LIB = $(TK_PREFIX)/lib
TCL_TK_SHLIB = $(TCL_TK_LIB)
TCLTK_SHLIB_SUFFIX = .so
diff -uNr /home/howarth/sparky/manual/Makefile /usr/local/src/sparky/manual/Makefile
--- /home/howarth/sparky/manual/Makefile 2001-11-13 18:37:53.000000000 -0500
+++ /usr/local/src/sparky/manual/Makefile 2002-12-20 22:48:27.000000000 -0500
@@ -65,13 +65,13 @@
rdist -R -c $(IMAGE_FILES) socrates:$(MANUAL_WWW)/images
manual.html: $(MANUAL_SECTIONS)
- htmlcat $(MANUAL_SECTIONS) > manual.html
+ ../bin/htmlcat $(MANUAL_SECTIONS) > manual.html
manual.ps: manual.html
echo 'Postscript Sparky manual needs updating'
make-manual.ps: manual.html
- html2ps manual.html > manual.ps
+ ../bin/html2ps manual.html > manual.ps
manual-postscript.gz: manual.ps
gzip -c manual.ps > manual-postscript.gz
diff -uNr /home/howarth/sparky/python/Makefile /usr/local/src/sparky/python/Makefile
--- /home/howarth/sparky/python/Makefile 2001-08-28 18:09:59.000000000 -0400
+++ /usr/local/src/sparky/python/Makefile 2002-12-21 13:34:53.000000000 -0500
@@ -5,8 +5,8 @@
INSTALL = \cp
SPARKY_INSTALL = /usr/local/sparky
-PYTHON_PREFIX = /usr/local
-PYTHON_VERSION = python1.5
+PYTHON_PREFIX = /usr
+PYTHON_VERSION = python2.1
PYTHON = $(PYTHON_PREFIX)/bin/$(PYTHON_VERSION)
PYTHON_LIB = $(PYTHON_PREFIX)/lib/$(PYTHON_VERSION)
@@ -28,7 +28,9 @@
tkutil.py volumeerror.py xeasy.py xplor.py
install: $(SPARKY_INSTALL)/python $(SPARKY_INSTALL)/python/sparky \
- $(SPARKY_INSTALL)/python/lib-tk
+ $(SPARKY_INSTALL)/python/lib-tk
+ mkdir -p $(SPARKY_INSTALL)/python $(SPARKY_INSTALL)/python/sparky \
+ $(SPARKY_INSTALL)/python/lib-tk
$(INSTALL) README $(SPARKY_INSTALL)/python
for pyfile in $(PYTHON_CODE) ; do \
$(INSTALL) $$pyfile $(SPARKY_INSTALL)/python/sparky ; \
----------------------------------------------------------------------
you will be able to do a 'make' and a 'make install'. At this point
if you 'cd /usr/local/sparky/bin' and run 'sparky-no-python' on
debian ppc sid the program starts up fine. However if you run
'sparky' instead, which uses the python extensions, you get a
segfault. I would really like to know if this is ppc specific or
if i386 sid sees this as well. Thanks in advance for helping with
this.
Jack
ps I plan to send any fixes we find upstream to the sparky maintainers.
Reply to: