[Bug]: linking error using DLIB_USE_MKL_WITH_TBB = ON
amwink opened this issue · 4 comments
What Operating System(s) are you seeing this problem on?
Linux (x86-64)
dlib version
19.24.4
Python version
3.11.8
Compiler
g++ 12.3.0-5
Expected Behavior
After seeing (with cmake-gui) that libraries mkl_tbb and mkl_tbb_thread are found and setting DLIB_USE_MKL_WITH_TBB to ON, for DLib to compile using the Intel-optimised routines.
Current Behavior
With DLIB_USE_MKL_WITH_TBB set to OFF, Compilation finishes, but with DLIB_USE_MKL_WITH_TBB set to ON, it gives these errors
dlib_errors_MKL_FFT.txt
Steps to Reproduce
With the switch set to OFF it compiles, with the switch set to ON it gives these linking errors.
Anything else?
Added the option '-ltbb' ( /usr/lib/x86_64-linux-gnu/libtbb.so points to libtbb.so.12.5 ) but CMake puts it at the start, when no symbols are added.
You don't need to use the TBB. But if you want to you will have to figure out how to link to it for your platform and send us a PR that makes cmake know how to do it :)
Warning: this issue has been inactive for 35 days and will be automatically closed on 2024-07-22 if there is no further activity.
If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search.
Warning: this issue has been inactive for 42 days and will be automatically closed on 2024-07-22 if there is no further activity.
If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search.
Notice: this issue has been closed because it has been inactive for 45 days. You may reopen this issue if it has been closed in error.