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

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