-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: call to undeclared function 'umfpack_di_defaults'; ISO C99 and later do not support implicit function declarations #471
Comments
This issue can be solved by adding: #include "../umfpack/src/umfpack/include/umfpack.h" right below the #include "../config.h" statement inside umf4_f77wrapper.c inside elmer/fem/src However beware of spiraling down into deeper compiler rabbitholes! |
This issue also breaks build with gcc14:
|
Have you tried with "EXTERNAL_UMFPACK=ON". This way you could use umfpack from SuiteSparse. It is a lot faster and more robust. The default version is ages old because at v. 5.1 UMFPACK license was changed from LGPL to GPL. |
@raback Thank you, this sounds good. I will try it and change the port to use it then in MacPorts. |
@ghostforest Bundled one works, though the path should be @raback And external seems to work, though gcc14 needs to disable these (trivially):
Since it is recommended, we will go with external one (that is also a preference of MacPorts generally). |
#488 would probably fix that build error. |
#488 has been merged to the devel branch. I guess this issue could be closed. |
@mmuetzel Incompatible pointers type error has not been addressed so far? |
@barracuda156: Thank you for the feedback. |
@mmuetzel I will try building the master and let you know. |
Yeah, ebd157e builds fine for me with gcc-14. |
I guess this can be closed then? |
I think so. |
I don't see
-Werror
in my build recipe anywhere but Clang 19 errors rather than warns on these C99 violations, breaking the build.Have you tried to build Elmer with recent versions of Clang? Is it expected to work?
The text was updated successfully, but these errors were encountered: