Blame SOURCES/bcc-0.14.0-loader-suggest-to-install-the-right-kernel-devel-pac.patch

0e54f6
From f7e7347dc1b4873f70a26392c997228999d346a8 Mon Sep 17 00:00:00 2001
0e54f6
From: Jerome Marchand <jmarchan@redhat.com>
0e54f6
Date: Wed, 10 Jun 2020 11:41:59 +0200
0e54f6
Subject: [PATCH 3/4] loader: suggest to install the right kernel devel package
0e54f6
0e54f6
Unfortunately, some package dependency system do not allow to make
0e54f6
sure that the kernel development package installed is the same version
0e54f6
as the running kernel. When this happen, the loader, unable to find
0e54f6
the kernel header, will suggest to rebuild the kernel with
0e54f6
CONFIG_IKHEADERS. For most users, this is probably not an option, but
0e54f6
installing the kernel development package corresponding to the running
0e54f6
kernel version is.
0e54f6
---
0e54f6
 src/cc/frontends/clang/loader.cc | 3 ++-
0e54f6
 1 file changed, 2 insertions(+), 1 deletion(-)
0e54f6
0e54f6
diff --git a/src/cc/frontends/clang/loader.cc b/src/cc/frontends/clang/loader.cc
0e54f6
index 9d768d30..79558dd3 100644
0e54f6
--- a/src/cc/frontends/clang/loader.cc
0e54f6
+++ b/src/cc/frontends/clang/loader.cc
0e54f6
@@ -151,7 +151,8 @@ int ClangLoader::parse(unique_ptr<llvm::Module> *mod, TableStorage &ts,
0e54f6
       kpath = tmpdir;
0e54f6
     } else {
0e54f6
       std::cout << "Unable to find kernel headers. ";
0e54f6
-      std::cout << "Try rebuilding kernel with CONFIG_IKHEADERS=m (module)\n";
0e54f6
+      std::cout << "Try rebuilding kernel with CONFIG_IKHEADERS=m (module) ";
0e54f6
+      std::cout <<  "or installing the kernel development package for your running kernel version.\n";
0e54f6
     }
0e54f6
   }
0e54f6
 
0e54f6
-- 
0e54f6
2.25.4
0e54f6