[Image-SIG] TkImaging on SGI?
Georg Mischler
schorsch@schorsch.com
Wed, 29 Sep 1999 07:10:30 -0400 (EDT)
> > Since some of the already installed libraries were compiled
> > that way, I had to use the -o32 option. Displaying images
> > with the Tk demos works fine, and PIL alone also doesn't
> > make any problems. The system is an O2 with irix 6.5 (I think
> > Python and Tk were compiled with an older OS version).
> >
> > Any suggestions where to look for fixing the problem?
>
> if you've change the Imaging.h structure, you may
> have to rebuild _tkinter (depending on where you've
> placed the tkImage.c module). If they doesn't match,
> getting a segmentation violation down in tkImage is
> quite likely.
This might explain some of the earlier funny errors I had,
which just mangled the images without dumping.
In this case here, the ImagingInstance is in its original
state (hmmm... except for the type string set to char[8]).
Another post suggested to compile with -n32 consistently,
which the friendly sysop will make possible as reccommended.
Thinking of it: what happens when _tkinter isn't set up
for _imaging at all (is this still necessary?)? Could
this cause a dump as well, or would it refuse to work
right away? I don't have root access to those systems,
so I haven't installed Python myself.
In any case, I think I hvae now three more places to look
for the source of the problem, one of which may well solve it.
Thanks so far!
-schorsch
--
Georg Mischler -- simulation developper -- schorsch at schorsch.com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/