Open dschwen opened 5 months ago
This must be something that just cropped up, right? What changed?
This just happened to me in deer as well. I don’t know what changed. I’m fine changing my definitions but I guess a better solution would be to do something more consistent than a hard coded function signature.
On Wed, Mar 27, 2024 at 15:05 Ben Spencer @.***> wrote:
This must be something that just cropped up, right? What changed?
— Reply to this email directly, view it on GitHub https://github.com/Argonne-National-Laboratory/neml/issues/170#issuecomment-2023751716, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZISQY3DFGDOD2QT3W6DB3Y2MKA3AVCNFSM6AAAAABFLO56SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTG42TCNZRGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
It turns out that this was due to a MOOSE change that added a #include "parse.h"
to pull in the framework/contrib/hit/parse.h
file, which has the same name as neml/include/parse.h
. That was fixed yesterday, and blackbear builds again.
These BLAS/Lapack forward declarations conflict with declaration we pull in through PETSc: https://github.com/Argonne-National-Laboratory/neml/blob/65c2ee4bbfb4f5499f17952e64ed87f85a1ef538/include/math/nemlmath.h#L17-L29
See compile error here: https://civet.inl.gov/job/2140682/
Ping @bwspenc