From: Borislav Petkov <bp@amd64.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>,
Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] tools: Add a toplevel Makefile
Date: Thu, 29 Mar 2012 13:21:56 +0200 [thread overview]
Message-ID: <20120329112156.GB6409@aftab> (raw)
In-Reply-To: <20120328175701.GB13426@aftab>
On Wed, Mar 28, 2012 at 07:57:01PM +0200, Borislav Petkov wrote:
> On Wed, Mar 28, 2012 at 11:51:25AM +0200, Borislav Petkov wrote:
> > I'm currently thinking I want to give the make tools/{perf,help,...}
> > approach a try because it is clear that it is a subdir of the kernel src
> > tree and it probably could support all the targets we thought about.
> >
> > Let me play around with it a bit...
>
> Yeah, nasty. I've almost got it to build a tool when doing
>
> $ make tools/<toolname>
>
> but it fails on all the targets which have implicit build rules. (It
> seems to build perf fine though because perf Makefile doesn't have
> implicit rules for %.c -> %.o etc). And I can see that implicit rules
> are being cleared in the toplevel kernel Makefile so that they don't
> kick in.
>
> At this moment, I'm open for hints from the kbuild people, if we use the
> toplevel Makefile to build tools/, should all the tools' Makefiles have
> explicit rules or ...? Any suggestions are appreciated.
Ok, I got it:
when make is run from the toplevel kernel Makefile, MAKEFLAGS contains
'--no-print-directory -RrI /home/boris/kernel/linux-2.6' which is
passed down to the sub-make and the '-r' especially turns off the use
of built-in implicit rules, thus the problem. Clearing MAKEFLAGS in the
sub-make fixes the issue, sorry for the noise.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-03-29 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:43 [PATCH 0/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 1/3] tools: Add Makefile.include Borislav Petkov
2012-03-23 14:43 ` [PATCH 2/3] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 3/3] tools: Add a help target Borislav Petkov
2012-03-24 7:44 ` [PATCH 0/2] tools: Add a toplevel Makefile Ingo Molnar
2012-03-26 12:26 ` Borislav Petkov
2012-03-26 14:05 ` Borislav Petkov
2012-03-26 15:14 ` Ingo Molnar
2012-03-26 15:41 ` Borislav Petkov
2012-03-28 7:25 ` Ingo Molnar
2012-03-28 9:51 ` Borislav Petkov
2012-03-28 17:57 ` Borislav Petkov
2012-03-29 11:21 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-22 17:01 Borislav Petkov
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=20120329112156.GB6409@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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