On Jul 3, 2014, at 8:37 AM, Jed Brown <[email protected]> wrote: > Satish Balay <[email protected]> writes: >> threadcomm.py is disabled in petsc3.4, 3.5. Should pthreadclasses.py also be >> disabled? [should openmp.py also be disabled?] >> >> https://bitbucket.org/petsc/petsc/commits/6e5884b57154c4018286842049a07306848380f9#chg-config/PETSc/packages/threadcomm.py > > Yes, they can't do anything but cause confusion right now, and the > legacy "pthreadclasses" option should go away.
Yes turn them all off.
