Source: kokkos Followup-For: Bug #1148650 It looks like kokkos is expecting applications to compile using the -fopenmp flag to avoid this error.
It can be fixed in the petsc configuration by including --with-openmp=1 alongside --with-kokkos=1 One might ask why petsc is not automatically adding openmp if kokkos needs it. I guess the answer is that kokkos does not "need" it. But since we've explicitly configured kokkos with openmp support, then petsc also needs to be likewise configured with openmp if it wants to use kokkos. One might then ask why petsc does not inspect the kokkos configuration to automatically determine whether it needs openmp or not. My guess for this is that the PETSc config system just checks direct package availability, which doesn't extend to indirect dependencies of the kind that we have here. PETSc doesn't use cmake. Looks like petsc: --with-openmp=1 is probably enough for resolving this bug, but I'll leave open a little longer to review the situation, including interaction with the HIP configurations. -- debian-science-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
