From: Jiri Olsa <jolsa@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org, pi3orama@163.com,
lizefan@huawei.com
Subject: Re: [PATCH v3 0/9] perf build: Make build-test faster
Date: Fri, 15 Jan 2016 11:20:05 +0100 [thread overview]
Message-ID: <20160115102005.GB4045@krava.brq.redhat.com> (raw)
In-Reply-To: <1452830421-77757-1-git-send-email-wangnan0@huawei.com>
On Fri, Jan 15, 2016 at 04:00:12AM +0000, Wang Nan wrote:
> Utilise Jiri's feature-dump make target to avoid make build-test check
> features too many times.
>
> v2 -> v3: add $(O_OPT) to 'make clean' to ensure the correctness of
> config-clean.
>
> Jiri Olsa (2):
> perf build: Add feature-dump target
> perf build: Introduce FEATURES_DUMP make variable
>
> Wang Nan (7):
> perf build: Set parallel making options build-test
> perf build: Pass O option to Makefile.perf in build-test
> perf build: Test correct path of perf in build-test
> perf build: Pass O option to kernel makefile in build-test
> tools build: Allow subprojects select all feature checkers
> perf build: Select all feature checkers for feature-dump
> perf build: Use feature dump file for build-test
>
> tools/build/Makefile.feature | 21 ++++++++++-
> tools/perf/Makefile.perf | 34 +++++++++++++++++-
> tools/perf/config/Makefile | 4 +++
> tools/perf/tests/make | 86 ++++++++++++++++++++++++++++++++++++--------
> 4 files changed, 128 insertions(+), 17 deletions(-)
got error on:
[jolsa@krava perf]$ make -f tests/make
Testing Makefile
readlink: missing operand
Try 'readlink --help' for more information.
- /BUILD_TEST_FEATURE_DUMP: cd . && make FEATURE_DUMP_COPY=/BUILD_TEST_FEATURE_DUMP feature-dump
cd . && make FEATURE_DUMP_COPY=/BUILD_TEST_FEATURE_DUMP feature-dump
tests/make:329: recipe for target '/BUILD_TEST_FEATURE_DUMP' failed
make[1]: *** [/BUILD_TEST_FEATURE_DUMP] Error 2
tests/make:7: recipe for target 'all' failed
make: *** [all] Error 2
next prev parent reply other threads:[~2016-01-15 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 4:00 [PATCH v3 0/9] perf build: Make build-test faster Wang Nan
2016-01-15 4:00 ` [PATCH v3 1/9] perf build: Set parallel making options build-test Wang Nan
2016-01-15 4:00 ` [PATCH v3 2/9] perf build: Pass O option to Makefile.perf in build-test Wang Nan
2016-01-19 13:35 ` [tip:perf/urgent] " tip-bot for Wang Nan
2016-01-15 4:00 ` [PATCH v3 3/9] perf build: Test correct path of perf " Wang Nan
2016-01-19 13:35 ` [tip:perf/urgent] " tip-bot for Wang Nan
2016-01-15 4:00 ` [PATCH v3 4/9] perf build: Pass O option to kernel makefile " Wang Nan
2016-01-19 13:35 ` [tip:perf/urgent] " tip-bot for Wang Nan
2016-01-15 4:00 ` [PATCH v3 5/9] perf build: Add feature-dump target Wang Nan
2016-01-15 19:11 ` Arnaldo Carvalho de Melo
2016-01-15 19:23 ` Arnaldo Carvalho de Melo
2016-01-15 19:27 ` Arnaldo Carvalho de Melo
2016-01-19 13:36 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2016-01-15 4:00 ` [PATCH v3 6/9] perf build: Introduce FEATURES_DUMP make variable Wang Nan
2016-01-19 13:36 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2016-01-15 4:00 ` [PATCH v3 7/9] tools build: Allow subprojects select all feature checkers Wang Nan
2016-01-15 4:00 ` [PATCH v3 8/9] perf build: Select all feature checkers for feature-dump Wang Nan
2016-01-15 4:00 ` [PATCH v3 9/9] perf build: Use feature dump file for build-test Wang Nan
2016-01-15 14:06 ` [PATCH v3 9/9 -fix] " Wang Nan
2016-01-15 14:08 ` [PATCH v3 9/9] " Wangnan (F)
2016-01-15 10:20 ` Jiri Olsa [this message]
2016-01-15 14:36 ` [PATCH v3 0/9] perf build: Make build-test faster Arnaldo Carvalho de Melo
2016-01-15 14:54 ` Arnaldo Carvalho de Melo
2016-01-15 14:54 ` pi3orama
2016-01-15 15:12 ` Arnaldo Carvalho de Melo
2016-01-15 16:33 ` Arnaldo Carvalho de Melo
2016-01-15 18:56 ` Arnaldo Carvalho de Melo
2016-01-15 19:01 ` Arnaldo Carvalho de Melo
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=20160115102005.GB4045@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.com \
--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;
as well as URLs for NNTP newsgroup(s).