[Python-Dev] Problems with 2.0b1 and GCC

Skip Montanaro skip@mojam.com (Skip Montanaro)
Thu, 6 Jul 2000 16:47:32 -0500 (CDT)

I thought I had this fixed, but apparently not.  On my Linux (Mandrake 6.1
with some stuff from 7.1), I'm getting the following traceback in certain
situations when running an oldish version of Zope (2.0.0):

    (gdb) bt
    #0  0x400712e8 in sigsuspend () from /lib/libc.so.6
    #1  0x401471a0 in __DTOR_END__ () from /lib/libc.so.6

Yesterday I removed pgcc and egcs (both were installed for some reason) and
upgraded the compilation environment to the following:


(Am I missing an important package that needs updating in the list above?) 

I had noticed the same traceback in test_fork1.py after I removed pgcc and
installed gcc 2.95 and friends, but before I realized I had egcs installed.
Deleting egcs cured the problem in at least some situations, but apparently
not all.

Anybody seen this?  I suspect it has something to do with threading (which
Zope requires).  My Python directory tree is up-to-date wrt the CVS
repository and was configured as

    ./configure  --with-threads --with-cycle-gc --prefix=/usr

and compiled as

    make OPT=-g

I will try turning off cycle-gc.  Any other thoughts from the assembled
compilation gurus?