From: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
To: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
linux-perf-users@vger.kernel.org
Subject: perf test LLVM failure
Date: Tue, 13 Jun 2017 10:40:37 +0200 [thread overview]
Message-ID: <95f0579d-ae99-1c6d-a19a-c79a77fea6e6@linux.vnet.ibm.com> (raw)
I have Fedora 25 with an 4.11 kernel and get this error
[root@s8360047 perf]# ./perf test LLVM
35: LLVM search and compile :
35.1: Basic BPF llvm compile : Ok
35.2: kbuild searching : Ok
35.3: Compile source for BPF prologue generation: FAILED!
35.4: Compile source for BPF relocation : Skip
[root@s8360047 perf]#
The error message is
libbpf: Program 'func=null_lseek file->f_mode offset orig'
contains non-map related relo data pointing to section 5
I have installed
clang-3.8.1-1.fc25.s390x
clang-libs-3.8.1-1.fc25.s390x
libpfm-4.8.0-2.ibm.fc25.s390x
compiler-rt-3.9.1-1.fc25.s390x
llvm-libs-3.8.1-2.fc25.s390x
and when I compile the test/bpf-script-test-prologue.c manually
the compile does not show any error message.
The error comes from file ../lib/bpf/libbpf.c
function bpf_program__collect_reloc()
Any ideas what cauese this and how to fix it?
By the way Fedora 24 with the same kernel version as above runs fine.
--
Thomas Richter, Dept 3303, IBM LTC Boeblingen Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2017-06-13 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 8:40 Thomas-Mich Richter [this message]
2017-06-16 16:09 ` perf test LLVM failure Arnaldo Carvalho de Melo
2017-06-19 0:34 ` Wangnan (F)
2017-06-19 7:45 ` Thomas-Mich Richter
2017-06-19 10:29 ` Wangnan (F)
2017-06-19 11:59 ` Thomas-Mich Richter
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=95f0579d-ae99-1c6d-a19a-c79a77fea6e6@linux.vnet.ibm.com \
--to=tmricht@linux.vnet.ibm.com \
--cc=brueckner@linux.vnet.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).