On Thu, 3 Jul 2014, Jed Brown wrote: > Baros Vladimir <[email protected]> writes: > > previously I successfully built PETSc with Intel compiler (the last > > successful build was 3.4.4) using OpenMP libraries. > > > > In version 3.5.0, OpenMP package depends on pthread library which > > doesn't exist on Windows. Why this new requirement and what do you > > recommend to use on Windows? > > Your old Windows configuration of PETSc was not actually using OpenMP. > > > The threaded implementations use a "thread communicator" which was > activated by the optional package "pthreadclasses". OpenMP is not used > by PETSc without "threadcomm" and we are refactoring the whole thing so > please don't use it at this time.
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 Satish
