chore(modern_bpf): use absolute path for clang executable

This is a very small change that should have no major impact on how the build works. However, when using ccache, having the clang executable resolve to the real path completely breaks compilation for the modern probe. Signed-off-by: Mauro Ezequiel Moltrasio <[email protected]>
falcosecurity · Aug 28, 2024 · e2c5174 · e2c5174
1 parent 3004d3e
commit e2c5174
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/driver/modern_bpf/CMakeLists.txt b/driver/modern_bpf/CMakeLists.txt
@@ -61,7 +61,7 @@ if(NOT MODERN_CLANG_EXE)
 endif()
 
 # If it is a relative path we convert it to an absolute one relative to the root source directory.
-get_filename_component(MODERN_CLANG_EXE "${MODERN_CLANG_EXE}" REALPATH BASE_DIR "${CMAKE_SOURCE_DIR}")
+get_filename_component(MODERN_CLANG_EXE "${MODERN_CLANG_EXE}" ABSOLUTE BASE_DIR "${CMAKE_SOURCE_DIR}")
 message(STATUS "${MODERN_BPF_LOG_PREFIX} clang used by the modern bpf probe: '${MODERN_CLANG_EXE}'")
 
 # Check the right clang version (>=12)