From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf BPF/elfdep intermitent build problems
Date: Thu, 19 Nov 2015 16:46:41 +0800 [thread overview]
Message-ID: <564D8C71.7050605@huawei.com> (raw)
In-Reply-To: <564D33F3.9050004@huawei.com>
On 2015/11/19 10:29, Wangnan (F) wrote:
>
>
> On 2015/11/19 10:21, Wangnan (F) wrote:
>>
[SNIP]
>> 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.
>
I understand this part of the problem.
There's no way for tools/build/Makefile.feature knowing whether
we are doing 'make clean' or 'make'. Therefore, even for
'make clean' those feature tests are mandatory to take action.
I posted a patch for it. Please see:
http://lkml.kernel.org/g/1447922706-99905-1-git-send-email-wangnan0@huawei.com
Thank you.
next prev parent reply other threads:[~2015-11-19 8:48 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)
2015-11-19 8:46 ` Wangnan (F) [this message]
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=564D8C71.7050605@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.