Ricardo Nabinger Sanchez

I still have the output from cmake: ``` ~/bcc/build$ cmake .. CMake Deprecation Warning at CMakeLists.txt:3 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of...

I've been able to build after a lot of tries, with this smallest diff: ```diff diff --git a/src/cc/CMakeLists.txt b/src/cc/CMakeLists.txt index ffe8feec..018afb9e 100644 --- a/src/cc/CMakeLists.txt +++ b/src/cc/CMakeLists.txt @@ -124,7 +124,7 @@...

Here's the most relevant part: ``` [ 38%] Building CXX object examples/cpp/CMakeFiles/CGroupTest.dir/CGroupTest.cc.o cd /home/rnsanchez/apps/bcc-copy/build/examples/cpp && /usr/bin/c++ -DHAVE_LIBDEBUGINFOD -I/usr/include/../tools/clang/include -I/home/rnsanchez/apps/bcc-copy/build/src/cc -I/home/rnsanchez/apps/bcc-copy/src/cc -I/home/rnsanchez/apps/bcc-copy/src/cc/api -I/home/rnsanchez/apps/bcc-copy/src/cc/libbpf/include/uapi -Wall -fPIC -O3 -DNDEBUG -std=gnu++14 -MD -MT examples/cpp/CMakeFiles/CGroupTest.dir/CGroupTest.cc.o...

> Looks like you are using LLVM 14 libraries ? Yes, 14.0.6, default with Slackware64-15.0 (and as of recent Slackware64-current).

> Cloud you please commet out line 156 and line 158 in CMakeLists.txt and see if it works? Done. The error persists: ``` make[2]: Entering directory '/home/rnsanchez/apps/bcc-copy/build' [ 38%] Building...

> > -- Found LLVM: /usr/include 13.0.0 (Use LLVM_ROOT envronment variable for another version of LLVM) > > No idea. Is there a mismatch between your LLVM toolchain and LLVM...

OK, based on your feedback, I decided to retrace all my steps and found out I was mistaken about the precise environment: * Slackware64-15.0 (fresh install) ships LLVM *13.0.0* ```...

Fix confirmed with https://github.com/iovisor/bcc/pull/4232/commits/b09d91d2196eebbe7d89ffcfbab4133fb5dc9abf.

> @rnsanchez Could you please check if this patch fix your issue #4214 ? Fix confirmed with the patch!

> Yes, thanks a lot. actually, i always compile with `-DENABLE_LLVM_SHARED=ON`, does @rnsanchez still have this problem, or just close this PR? For me, your proposed patch did the trick...