From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Wangnan (F)" <wangnan0@huawei.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf BPF/elfdep intermitent build problems
Date: Fri, 27 Nov 2015 12:15:01 -0300 [thread overview]
Message-ID: <20151127151501.GC5934@kernel.org> (raw)
In-Reply-To: <564D33F3.9050004@huawei.com>
Em Thu, Nov 19, 2015 at 10:29:07AM +0800, Wangnan (F) escreveu:
> 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?
Some build problem just happened and your question came to my mind,
yeah, sometimes I NFS mount it from a RHEL6 (and other distros) to do
'make -C tools/perf build-test' to check it works with those distros,
and I forgot to do a:
make -C tools/ clean
I guess I'll have to try to make build-test support O=... So that
polluting the source tree doesn't causes problems like this.
Will try even to make it turn the source tree read only so that we spot
when O= is not being honoured...
- Arnaldo
next prev parent reply other threads:[~2015-11-27 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 22:44 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)
2015-11-19 8:46 ` Wangnan (F)
2015-11-27 15:15 ` Arnaldo Carvalho de Melo [this message]
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=20151127151501.GC5934@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome