https://bugzilla.redhat.com/show_bug.cgi?id=1350257
--- Comment #36 from Antonio Trande <anto.trande(a)gmail.com> ---
(In reply to Dave Love from comment #35)
The fact that the check behaves differently in local mock, koji, and
copr
suggests a real problem with undefined behaviour, which I think we should
worry about; I don't have time to debug it. Maybe orion has an opinion, as
he's watching?
Regarding the unused-direct-shlib-dependencys, I meant to find out why the
configured libraries aren't getting used, rather than just adding
--as-needed. It seems to be a build bug, but again I don't have time to
investigate. It's the sort of thing I might raise a bug report about as a
user of the package, and the packaging I did of older versions didn't have
this issue, e.g. metis is used.
I didn't notice before that fftw isn't configured because there's no bcond
for it. It's an example of the conditionals being confusing when they don't
have an obvious purpose. Is there any reason not to build against fftw?
PETSc needs fftw-mpi libraries; it does not work with fftw actually available
on Fedora/EPEL.
Also, I still don't understand the module file. The tests run (locally, for
me)
without it, so why is it needed?
Sorry, which modules?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component