linux-kernel - Re: [PATCH 2/2] perf tools: Always try to build libtraceevent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120523014317.GE19247@infradead.org>
Date:	Tue, 22 May 2012 22:43:17 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Namhyung Kim <namhyung.kim@....com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH 2/2] perf tools: Always try to build libtraceevent

Em Wed, May 23, 2012 at 10:13:55AM +0900, Namhyung Kim escreveu:
> Hi,
> 
> On Tue, 22 May 2012 12:36:48 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, May 22, 2012 at 06:03:54PM +0900, Namhyung Kim escreveu:
> >> While at it, silence annoying directory change messages.
> >
> > Applied, have you seen these?
> >
> > make[1]: Entering directory `/home/git/linux/tools/lib/traceevent'
> > make[2]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
> > make[2]: `libtraceevent.a' is up to date.
> 
> Yes, but I didn't know how to handle them properly. And the first line
> looks like a bug of QUIET_SUBDIR stuff. Did you build it out of the
> kernel tree?

I always use:

[acme@...dy linux]$ make -j8 -C tools/perf/ O=/home/git/build/perf install

- Arnaldo
--
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/