Closed sphamil closed 4 months ago
@trilinos/tpetra @trilinos/kokkos-kernels
@srajama1
Small update, linking from an external package is not necessary to reproduce. Turning on Trilinos_ENABLE_TESTS
in the above configure script results in link errors from the Tpetra/Kokkos-Kernels unit tests.
This does seem to be identical to #11033 @lucbv said he'd look into it.
@sphamil Is this working for you now?
This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE
label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE
.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.
This issue was closed due to inactivity for 395 days.
@trilinos/tpetra @trilinos/kokkos-kernels
Description
We're encountering a problem linking against Trilinos 13.4 (undefined reference to
spmv
) from an external project when it is built with Intel MKL as a TPL. No issue is observed with Trilinos 13.2. When building withdevelop
we get a Trilinos build error that I believe is identical to #11033. When MKL is disabled as a TPL (but still used as the BLAS/LAPACK implementation), no error is observed. Disabling MKL is not a viable option as the Pardiso MKL solver is our primary preconditioner option for the application.Steps to Reproduce
nm --demangle libtpetra.so | grep "spmv("
: nm_tpetra.txtnm --demangle libkokkoskernels.so | grep "spmv("
: nm_kokkoskernels.txtActual external project is export controlled, but I can put together a minimal external project that reproduces the issue if necessary.