Can't build 2.7.0 with GCC 11.2.0.
1uc opened this issue · 1 comments
1uc commented
Thank you for this useful toolbox and its nice packaging, e.g. in spack. I'm unable to build v2.7.0
on my machine (GCC 11.2.0, CMake 3.23.0), while master
works flawlessly.
I'm building Caliper as follows:
git clone https://github.com/LLNL/Caliper.git && cd Caliper
git checkout v2.7.0
cmake -DCMAKE_INSTALL_PREFIX=${HOME}/tmp_caliper -DCMAKE_BUILD_TYPE=Release -B build
cmake --build build --verbose
which terminates with:
[ 98%] Linking CXX executable cali-query
cd /home/lucg/git/bbp/Caliper/build-2.7.0/src/tools/cali-query && /usr/bin/cmake -E cmake_link_script CMakeFiles/cali-query.dir/link.txt --verbose=1
/usr/bin/c++ -O3 -DNDEBUG -rdynamic "CMakeFiles/cali-query.dir/AttributeExtract.cpp.o" "CMakeFiles/cali-query.dir/cali-query.cpp.o" "CMakeFiles/query-common.dir/query_common.cpp.o" -o cali-query -Wl,-rpath,/home/lucg/git/bbp/Caliper/build-2.7.0/src/tools/util:/home/lucg/git/bbp/Caliper/build-2.7.0/src: ../util/libcaliper-tools-util.so.2.7.0 ../../libcaliper-serial.so.2.7.0
/usr/bin/ld: ../../libcaliper-serial.so.2.7.0: undefined reference to `_dl_sym'
collect2: error: ld returned 1 exit status
The same steps for caliper@master
runs through with the corresponding line for cali-query
[ 98%] Linking CXX executable cali-query
cd /home/lucg/git/bbp/Caliper/build-master/src/tools/cali-query && /usr/bin/cmake -E cmake_link_script CMakeFiles/cali-query.dir/link.txt --verbose=1
/usr/bin/c++ -O3 -DNDEBUG -rdynamic "CMakeFiles/cali-query.dir/AttributeExtract.cpp.o" "CMakeFiles/cali-query.dir/cali-query.cpp.o" "CMakeFiles/query-common.dir/query_common.cpp.o" -o cali-query -Wl,-rpath,/home/lucg/git/bbp/Caliper/build-master/src/tools/util:/home/lucg/git/bbp/Caliper/build-master/src: ../util/libcaliper-tools-util.so.2.8.0-dev ../../libcaliper-serial.so.2.8.0-dev
make[2]: Leaving directory '/home/lucg/git/bbp/Caliper/build-master'
[ 98%] Built target cali-query
I'm unable to spot a relevant difference in the two commands for linking cali-query
.
Since the problem is resolved on master
I wanted to ask if it's possible to release a new version?
jrmadsen commented
master probably has some form of this fix: LLNL/GOTCHA#101.