On Mon, 25 Jun 2001, James Henstridge wrote:
> > This only happens when I omit --disable-threads from my configure line. If
> > I allow threads, boom. (As you have pointed out below, it matters).
>
> threading is disabled by default, as it doesn't work correctly with glib
> 2.0 (if anyone on the list is a python threading guru and would like to
> help, some of the details are in the pygtk/THREADING file in CVS). If you
> don't touch the --{enable,disable}-thread option, things should build
> correctly.
Sorry, I've been on too much crack to make sense lately. What I _menat_ to
say was "When I run plain ./configure with _no_ parameters whatsoever my
pygtk compile bombs out".
All my builds compiled fine (no warnings at all). It was upon program
execution (on exit of hello2.py, for example) that the segmentation fault
showed.
Compiling --enable-threads _also_ bombs out, of course.
> > Is there another way I can track this down?
>
> Don't use --enable-thread :)
I didn't. With no parameters to ./configure, pygtk SEGVed on me.
When I supplied --disable-threads it stopped SEGVing.
When I supplied --enable-threads AND linked just about everything that
starts with lib and lives under /usr/local/lib with -lpthread it didn't
SEGV either. I don't think _that_ is what you're referring to when you
mention "Threading Problems under Python." :-)
Hope that's more clear.
Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
