https://bugzilla.redhat.com/show_bug.cgi?id=2510919
--- Comment #29 from UW_Linux <[email protected]> --- > Sure, but is that a meaningful option that either we or upstream should still > be providing. MPI variants is already proving how that complexity can blow in > our face. I have not dig deep into how these 2 variants interact but I > believe it was safe to use the openmp variant and would not collide with the > consumer's usage, other than the common environment variable that controls > the parallelization there. But it's worth reopening the issue with upstream. I think so, and I'd perfer building `elpa_openmp` only for Fedora RPM build as OpenMP library is shipped with GCC anyways. But https://gitlab.com/QEF/q-e/-/merge_requests/2890#note_3550770203 seems to argue that linking elpa_openmp to a non-OpenMP build might cause failure. I didn't investigate them, but if that is true then this would be relevant. -- You are receiving this mail because: You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2510919 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202510919%23c29 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
