Cmake warnings when installing from source (unclear if they are problematic)

[benrhodes26]

I get the following warnings when installing from source.

It seems that I can still run ggcaller without error, but should I be worried about any unexpected behaviour?

CMake Warning at .../mamba/envs/ggc_env/lib/python3.9/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:22 (message):
  static library kineto_LIBRARY-NOTFOUND not found.
Call Stack (most recent call first):
 .../mamba/envs/ggc_env/lib/python3.9/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:127 (append_torchlib_if_found)
  CMakeLists.txt:81 (find_package)

-- Configuring done
CMake Warning at ..../mamba/envs/ggc_env/share/cmake/pybind11/pybind11Tools.cmake:177 (add_library):
  Cannot generate a safe runtime search path for target ggCaller_cpp because
  files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libmkl_intel_ilp64.so] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
     .../mamba/envs/ggc_env/lib
    runtime library [libmkl_sequential.so] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
     .../mamba/envs/ggc_env/lib
    runtime library [libmkl_core.so] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
      .../mamba/envs/ggc_env/lib

  Some of these libraries may not be found correctly.
Call Stack (most recent call first):

  CMakeLists.txt:22 (pybind11_add_module)

[samhorsfield96]

Hi Ben, I wouldn't expect this warning to affect results if ggCaller runs to completion. If the wrong MKL library were to be loaded, it would likely cause a runtime error and crash.

[benrhodes26]

great, thanks for the advice 👍