.dynsym local symbol at index XX

Hi all,

I keep getting warnings when linking against libComputeCpp.so. The code runs just fine, but I would like to make sure I am not doing something wrong. This happens even when building a C++ code with a trivial main function and no SYCL code.

My CMakeLists.txt file looks like this:

cmake_minimum_required(VERSION 3.15)


find_package(ComputeCpp REQUIRED)



target_compile_features(SYCLtest PRIVATE cxx_std_17)

add_sycl_to_target(TARGET SYCLtest SOURCES main.cpp)

CMake configuration seems to be running just fine:

$ cmake -DComputeCpp_DIR=/opt/ComputeCpp-CE ..
-- The CXX compiler identification is GNU 10.1.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for CL_VERSION_2_2
-- Looking for CL_VERSION_2_2 - found
-- Found OpenCL: /usr/lib/libOpenCL.so (found version "2.2") 
-- platform - your system can support ComputeCpp
-- Found ComputeCpp: /opt/ComputeCpp-CE (found version "CE 1.3.0") 
-- compute++ flags - -O2;-mllvm;-inline-threshold=1000;-intelspirmetadata;-sycl-target;spir64
-- Configuring done
-- Generating done

However, I consistently get two warnings when building the code (which consists of a main function returning 0):

$ cmake --build .
Scanning dependencies of target SYCLtest_main.cpp_0_ih
[ 33%] Building ComputeCpp integration header file /myPath/syclTest/build/SYCLtest_main.cpp.sycl
[ 33%] Built target SYCLtest_main.cpp_0_ih
Scanning dependencies of target SYCLtest
[ 66%] Building CXX object CMakeFiles/SYCLtest.dir/main.cpp.o
[100%] Linking CXX executable SYCLtest
/usr/bin/ld: /opt/ComputeCpp-CE/lib/libComputeCpp.so: .dynsym local symbol at index 213 (>= sh_info of 1)
/usr/bin/ld: /opt/ComputeCpp-CE/lib/libComputeCpp.so: .dynsym local symbol at index 214 (>= sh_info of 1)
[100%] Built target SYCLtest

I am running Arch Linux with ComputeCpp-CE. Am I missing something? Thanks!

Hi Joachim,
It looks like it is probably a harmless warning.
You could try updating binutils, as this issue suggests.