matteosal edited a comment on issue #20301: URL: https://github.com/apache/incubator-mxnet/issues/20301#issuecomment-876522230
Linking to `libmkl_rt` without setting special MKL environment variables is equivalent to linking to the LP64 version of MKL: https://software.intel.com/content/www/us/en/develop/documentation/onemkl-linux-developer-guide/top/linking-your-application-with-the-intel-oneapi-math-kernel-library/linking-quick-start/using-the-single-dynamic-library.html This is confirmed by your `MKL_VERBOSE` output, reporting `lp64`. So this is a no go for me, as I have to use ILP64. But this is also telling us that the problem is likely to be about some integer size mismatch. One way to confirm this is to run the example with the library linked to libmkl_rt specifying `MKL_INTERFACE_LAYER=ILP64` (https://software.intel.com/content/www/us/en/develop/documentation/onemkl-linux-developer-guide/top/linking-your-application-with-the-intel-oneapi-math-kernel-library/linking-in-detail/dynamically-selecting-the-interface-and-threading-layer.html). I expect it to crash in this case. Another test is to go back to passing all the `BLAS_LIBRARIES` explicitly, but specifying the LP64 version there and in `BLA_VENDOR`. This setup should not crash. I'm trying to test these setups myself but I'm having other kinds of unrelated problems blocking me right now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
