From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf BPF/elfdep intermitent build problems
Date: Wed, 18 Nov 2015 19:44:58 -0300 [thread overview]
Message-ID: <20151118224458.GD22729@kernel.org> (raw)
Have you guys ever saw this?
[acme@zoo linux]$ alias m
alias m='perf stat -e cycles make O=/tmp/build/perf -C tools/perf
install-bin'
[acme @zoo linux]$ m
make: Entering directory '/home/git/linux/tools/perf'
BUILD: Doing 'make -j4' parallel build
make[2]: Nothing to be done for 'fixdep'.
CC /tmp/build/perf/util/machine.o
LD /tmp/build/perf/util/libperf-in.o
No libelf found
BPF API too old
Makefile:191: recipe for target 'elfdep' failed
make[2]: *** [elfdep] Error 255
make[2]: *** Waiting for unfinished jobs....
Makefile:194: recipe for target 'bpfdep' failed
make[2]: *** [bpfdep] Error 255
Makefile.perf:434: recipe for target '/tmp/build/perf/libbpf.a' failed
make[1]: *** [/tmp/build/perf/libbpf.a] Error 2
make[1]: *** Waiting for unfinished jobs....
LD /tmp/build/perf/libperf-in.o
Makefile:87: recipe for target 'install-bin' failed
make: *** [install-bin] Error 2
make: Leaving directory '/home/git/linux/tools/perf'
Performance counter stats for 'make O=/tmp/build/perf -C tools/perf
install-bin':
10,265,920,369 cycles
3.002799545 seconds time elapsed
[acme@zoo linux]$
If I go and try doing a clean on the libbpf dir I see another problem:
[acme@zoo linux]$ cd tools/lib/bpf
[acme@zoo bpf]$ make clean
Auto-detecting system features:
... libelf: [ OFF ]
... bpf: [ OFF ]
CLEAN libbpf
CLEAN core-gen
[acme@zoo bpf]$
No need for feature detection when doing a plain 'make clean', right?
But then, after cleaning it again, and entering tools/perf to do a 'make
clean' as well, it does the feature detection at a second 'make clean'
and this time it shoes [ on ] for both libelf and bpf, and this time
I manage to build perf.
This is all intermitent, will eventually try to drill down if you don't
fix it first
- Arnaldo
next reply other threads:[~2015-11-18 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 22:44 Arnaldo Carvalho de Melo [this message]
2015-11-19 1:24 ` perf BPF/elfdep intermitent build problems Wangnan (F)
2015-11-19 2:21 ` Wangnan (F)
2015-11-19 2:29 ` Wangnan (F)
2015-11-19 8:46 ` Wangnan (F)
2015-11-27 15:15 ` Arnaldo Carvalho de Melo
2015-11-19 11:50 ` Wangnan (F)
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=20151118224458.GD22729@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangnan0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.