From: "Wangnan (F)" <wangnan0@huawei.com>
To: <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] tools/Makefile: Fix Many Many problems and inconsistencies
Date: Tue, 2 Aug 2016 12:53:23 +0800 [thread overview]
Message-ID: <57A02743.1080208@huawei.com> (raw)
In-Reply-To: <0e76826b-6552-e880-42fc-17be0c5bf3fe@infradead.org>
On 2016/8/2 11:46, Randy Dunlap wrote:
> and subdir Makefiles.
>
> Examples:
>
> Use/honor O=outputdir consistently instead of building in <kerneltree>/tools.
> (check/compare kernel commit bf35182ffcd00d8b36d56210ffdac110e5624d7d)
>
> Honor MAKEFLAGS (well, they aren't even passed to tools/Makefile AFAICT.
> from an execution log:
> make LDFLAGS= MAKEFLAGS="" O=/local/lnx/kernel/lnx-47/TOOLS subdir=tools -C ../tools/ all
>
> Use make's "findstring" correctly (see patch below)
>
> There are lots of other problems unless I have just had too much too drink tonight,
> so here's the TECH TOPIC:
>
> In a 1.5 hour code crunch session, get a bunch of interested people together to fix
> a lot of problems quickly. Then I will be a guinea pig tester. :)
>
>
> Self-nomination: /me.
> Others interested:
> Arnaldo (acme); Michal Marek.
Please count me in. I worked in tools/Makefile and tools/perf/Makefile,
solved
some problems to make it work for my cross-compiling environment. 'O='
is important
to me.
Thank you.
next prev parent reply other threads:[~2016-08-02 4:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 3:46 Randy Dunlap
2016-08-02 4:53 ` Wangnan (F) [this message]
2016-08-03 19:00 ` Arnaldo Carvalho de Melo
2016-08-02 5:02 ` Josh Triplett
2016-08-02 7:31 ` Arnd Bergmann
2016-08-02 8:27 ` Josh Triplett
2016-08-02 8:41 ` Alexandre Belloni
2016-08-02 8:43 ` Josh Triplett
2016-09-04 21:15 ` Ben Hutchings
2016-09-06 14:57 ` Arnaldo Carvalho de Melo
2016-09-08 3:25 ` Bamvor Zhang Jian
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=57A02743.1080208@huawei.com \
--to=wangnan0@huawei.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox