Configuration crash - can't start new thread

[Matthew Knepley]

You have a broken Python installation. You can work around this using
the options --useThreads=0.

  Thanks,

    Matt

On 12/5/06, Ben Tay <zonexo at gmail.com> wrote:
> Hi,
>
> I tried to compile the library on a linux sys (xeon). It gives the error
> msg:
>
>
>
> *********************************************************************************
>           CONFIGURATION CRASH  (Please send configure.log to
> petsc-maint at mcs.anl.gov)
> *********************************************************************************
>
> can't start new thread
>
>   File "./config/configure.py", line 172, in petsc_configure
>     framework =
> config.framework.Framework(sys.argv[1:]+['--configModules=PETSc.Configure','--optionsModule=PETSc.compilerOptions'],
> loadArgDB = 0)
>   File
> "/nas/hpctmp/g0306332/petsc-2.3.2-p7/python/BuildSystem/config/framework.py",
> line 81, in __init__
>     self.argDB['debugSections'] = ['screen']
>   File "/nas/hpctmp/g0306332/petsc-2.3.2-p7/python/BuildSystem/RDict.py",
> line 219, in __setitem__
>     self.save()
>   File "/nas/hpctmp/g0306332/petsc-2.3.2-p7/python/BuildSystem/RDict.py",
> line 639, in save
>     self.saveTimer.start()
>   File "/usr/lib/python2.2/threading.py", line 396, in
> start
>     _start_new_thread(self.__bootstrap, ())
>
>
> May I know what's wrong? I also can't find any configure.log file.
>
> Thank you.
>
> Regards


-- 
"Failure has a thousand explanations. Success doesn't need one" -- Sir
Alec Guiness