linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Perf tool build with clang/llvm support broken
Date: Tue, 11 Jul 2023 12:22:15 +0200	[thread overview]
Message-ID: <648ac57d-0578-30cb-2cd8-577e1016442e@linux.ibm.com> (raw)

I would like to build the perf tool with LLVM/CLANG support and did

# make LIBCLANGLLVM=1 
  BUILD:   Doing 'make -j2' parallel build
  Warning: Kernel ABI header at 'tools/include/uapi/linux/perf_event.h' differs...
  ... some more similar lines removed.

  Makefile.config:1120: No suitable libLLVM found, disabling builtin clang and LLVM support. 
  Please install llvm-dev(el) (>= 3.9.0)

However when I check llvm packages, I do have them installed on that machine:

 # rpm -qa | grep llvm
 llvm-libs-16.0.3-1.fc38.x86_64
 llvm-16.0.3-1.fc38.x86_64
 llvm-test-16.0.3-1.fc38.x86_64
 llvm-static-16.0.3-1.fc38.x86_64
 llvm-devel-16.0.3-1.fc38.x86_64

 # rpm -qa | grep clang
 clang-resource-filesystem-16.0.3-1.fc38.x86_64
 clang-libs-16.0.3-1.fc38.x86_64
 clang-tools-extra-16.0.3-1.fc38.x86_64
 clang-16.0.3-1.fc38.x86_64
 clang-devel-16.0.3-1.fc38.x86_64
 git-clang-format-16.0.3-1.fc38.x86_64
[root@f38 ~]#

This shows up on s390x and x86_64 (my virtual machine).
Any ideas have to fix this? Am I missing a package?

Thanks.
-- 
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

             reply	other threads:[~2023-07-11 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 10:22 Thomas Richter [this message]
2023-07-13  2:51 ` Perf tool build with clang/llvm support broken Ian Rogers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=648ac57d-0578-30cb-2cd8-577e1016442e@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).