[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130401210550.GA20670@krava.redhat.com>
Date: Mon, 1 Apr 2013 23:05:51 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Sam Ravnborg <sam@...nborg.org>
Cc: linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Borislav Petkov <bp@...en8.de>, Michal Marek <mmarek@...e.cz>,
linux-kbuild@...r.kernel.org, Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 27/27] perf tools: Add kbuild support into Makefile.kbuild
On Mon, Apr 01, 2013 at 10:03:42PM +0200, Sam Ravnborg wrote:
> On Mon, Apr 01, 2013 at 09:18:50PM +0200, Jiri Olsa wrote:
> > Adding kbuild support into Makefile.kbuild. The 'legacy'
> > Makefile still stays untouched as it was.
>
> When readign the Kbuild file I get confused.
> the obj-y syntax is used for kernel built-in stuff,
> and obj-m for modules.
> I had expected either a perf specific syntax or something like the
> syntax used for host programs.
While building kernel you need to have separate flags
for internal objects and for host programs.
First, I thought I need to separate it as you say, but
perf build is separated from kernel built process, so
AFAICS we can use obj-y with no harm in perf.
It's quite possible I missed something and kbuild folks
prove me wrong ;-)
The Makefile.kbuild defines flags to be used for obj-y.
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists