From: Ben Hutchings <ben@decadent.org.uk>
To: Randy Dunlap <rdunlap@infradead.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Cc: Michal Marek <mmarek@suse.cz>,
Arjan van de Ven <arjan@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] tools/Makefile: Fix Many Many problems and inconsistencies
Date: Sun, 04 Sep 2016 22:15:02 +0100 [thread overview]
Message-ID: <1473023702.25374.119.camel@decadent.org.uk> (raw)
In-Reply-To: <0e76826b-6552-e880-42fc-17be0c5bf3fe@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
[Slowly catching up on ksummit-discuss]
On Mon, 2016-08-01 at 20:46 -0700, 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. :)
[...]
I don't know how much can be done in that time. I've had some
recurring pains in packaging tools/:
1. Many different build systems
- Inconsistent support for configuration variables (not just 'O')
- usbip isn't included in a recursive build, presumably because
it uses autotools
2. Tools include UAPI headers in one of two ways, neither of which is
reliable:
- Assume the current headers are on the system include path
- Include unprocessed UAPI headers through a relative path
The right thing to do is to run 'make headers_install' and add
usr/ to the front of the system include path. But we'd want a
way to avoid re-doing that when the UAPI headers haven't changed.
3. Tools frequently fail to build in stable releases (sometimes on
specific architectures) - seems like tools/ is not covered by CI
or it's ignored
This last point is more of a core topic though.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-04 21:15 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)
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 [this message]
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=1473023702.25374.119.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=arjan@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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