Baros Vladimir <[email protected]> writes: > So it could be that the external packages were using OpenMP because > compiled applications from my build require an openmp dll.
Are you using --download for them? Why does PETSc need to be built with openmp? > With this build I compiled a static version of pthreads-win32 from here: > https://www.sourceware.org/pthreads-win32/ > > and PETSc compiled with those libs. Also configuration stage passed without > problems. > > But at the end the tests failed with the unresolved > PetscThreadCommCreate_PThread The options --with-pthread, --with-pthreadclasses, and --with-openmp are not orthogonal in the current version (i.e., the preprocessor macros do not support all the combinations). It doesn't make sense to "fix" because we're refactoring in a significant way and the current version is too fragile about issues like affinity. Just don't use any of it right now. External packages are welcome to use OpenMP and I expect we'll have the better system out by the end of summer.
pgpmus_J0iEbl.pgp
Description: PGP signature
