|
From: Jens V. <je...@zo...> - 2002-04-30 19:08:08
|
the cycle-gc option should be safe again in python-2.1.3. it was rooted=20= out after enough people complained about their Zope servers segfaulting,=20= cycle-gc had a bug in it that was consequently fixed for 2.1.3 jens On Tuesday, April 30, 2002, at 02:12 , Michael Str=F6der wrote: > Jan Idzikowski wrote: > > > > i have a problem with the ldap-module on AIX. > > Disclaimer: I have no personal experience on AIX and > IBM's C compiler. > > > I use Python-2.1.3 installed thread-safe with the IBM > > C-Compiler cc_r and the option -qmaxmem=3D4000. > > I also have no clue what "Python-2.1.3 installed thread-safe" means. > > But please check the options you chose when compiling Python by = issuing=20 > the following command in Python's source tree. > > $ ./configure --help > > Some candidates for further examination might be: > > --without-gcc never use gcc > --with-signal-module disable/enable signal module > --with(out)-threads[=3DDIRECTORY] disable/enable thread support > --with(out)-thread[=3DDIRECTORY] deprecated; use > --with(out)-threads > --with-pth use GNU pth threading libraries > --with(out)-cycle-gc disable/enable garbage collection > --with(out)-pymalloc disable/enable specialized mallocs > --with-wctype-functions use wctype.h functions > --with-dl-dld=3DDL_DIR,DLD_DIR GNU dynamic linking > --with-fpectl enable SIGFPE catching > > At least on Linux I had to stay away of using cycle-gc and pymalloc.=20= > (Check list archive!) > > Ciao, Michael. > > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |