I just built and tested 2.0b2 on Slackware 7.0, and found that threads failed miserably. I got the message: pthread_cond_wait: Interrupted system call over & over (*hundreds* of times before I killed it) during one of the tests (test_fork1.py? it scrolled out of the scollback buffer, 2000 lines). If I configure it --without-threads it works great. Unless you need threads. uname -a says: Linux linux1.compile.sourceforge.net 2.2.14-5.0.14smp #1 SMP Sun Mar 26 13:03:52 PST 2000 i686 unknown ldd ./python says: libdb.so.3 => /lib/libdb.so.3 (0x4001c000) libdl.so.2 => /lib/libdl.so.2 (0x40056000) libutil.so.1 => /lib/libutil.so.1 (0x4005a000) libm.so.6 => /lib/libm.so.6 (0x4005d000) libc.so.6 => /lib/libc.so.6 (0x4007a000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) If anyone has any ideas, please send them along! I'll turn this into a real bug report later. -Fred -- Fred L. Drake, Jr. <fdrake at beopen.com> BeOpen PythonLabs Team Member
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4