Re: clue on sparky

Jack Howarth <[EMAIL PROTECTED]> writes: > 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 pytho

Re: clue on sparky

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

Re: clue on sparky

Jack Howarth <[EMAIL PROTECTED]> writes: > 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 o

sparky problems resolved

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