From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf BPF/elfdep intermitent build problems
Date: Thu, 19 Nov 2015 10:29:07 +0800 [thread overview]
Message-ID: <564D33F3.9050004@huawei.com> (raw)
In-Reply-To: <564D323A.1050200@huawei.com>
On 2015/11/19 10:21, Wangnan (F) wrote:
>
>
> On 2015/11/19 9:24, Wangnan (F) wrote:
>>
>>
>> On 2015/11/19 6:44, Arnaldo Carvalho de Melo wrote:
>>> 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
>>
>> This error message means the kernel header in rootfs is too old,
>> causes tools/build/feature/test-bpf.c failed to be built.
>
> Strange... even in feature detection it should check BPF API through
> kernel source where you are using to build perf...
>
> I guess you are not using NFS or share it with other people?
>
>>
>>> 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?
>>>
>
> Right. It should be
>
> $ cd tools/lib/bpf
> $ make clean
> CLEAN libbpf
> CLEAN core-gen
> $
>
>
> After cleaning can you trigger this problem again?
>
Tiggered part of your problem:
$ make
Auto-detecting system features:
... libelf: [ on ]
... bpf: [ on ]
CC libbpf.o
CC bpf.o
LD libbpf-in.o
LINK libbpf.a
LINK libbpf.so
$ make clean
CLEAN libbpf
CLEAN core-gen
$ make clean
Auto-detecting system features:
... libelf: [ on ]
... bpf: [ on ]
CLEAN libbpf
CLEAN core-gen
Feature check would be triggered the second time we make clean.
Will look into it.
Thank you.
next prev parent reply other threads:[~2015-11-19 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 22:44 perf BPF/elfdep intermitent build problems Arnaldo Carvalho de Melo
2015-11-19 1:24 ` Wangnan (F)
2015-11-19 2:21 ` Wangnan (F)
2015-11-19 2:29 ` Wangnan (F) [this message]
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=564D33F3.9050004@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@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 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.