-
Notifications
You must be signed in to change notification settings - Fork 579
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
libtpetraclassic.so misses dependency information #933
Comments
@nschloe Could you please explain how this affects build correctness? Thanks! |
Well, this means that if you try to link an executable against that library, you'll have to explicitly link all its dependent libraries as well (although you're not directly using them). Typically, you'll find that only some dynamic library link info is missing (and can be detected with
i.e., there's only one object in there:
Indeed,
That can't be right, can it? |
It's my understanding that TpetraClassic is a placeholder, that we need for backwards compatibility, during the transition to the new Tpetra stack (which is rather complete?). Looking at the TpetraClassic code your observations are not surprising. I guess, TpetraClassic will go away at some point. |
@tawiesn wrote:
That's correct. It doesn't have any meaningful contents, except perhaps for an enum definition and some headers that remain for backwards compatibility. It will go away at some point. |
Alright, I guess the Debian warnings are safe to ignore. Thanks for the explanation! |
When building just Tpetra, e.g., like so
everything seems to be going fine. However, the two libraries
libtpetraclassic.so
andlibtpetraclassiclinalg.so
come without dependency information:All other libraries seem fine:
I can't quite see what's going wrong yet. Any ideas? @mhoemmen @bartlettroscoe
The text was updated successfully, but these errors were encountered: