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: <CAFTL4hxo3aQT32RZT64wjARYiGLTkvAvKUuoQZw81mTDXdS8nA@mail.gmail.com>
Date:	Mon, 9 Apr 2012 19:10:47 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Borislav Petkov <bp@...en8.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <srostedt@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>, Arun Sharma <asharma@...com>,
	Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH 03/15] perf: Build libtraceevent.a

2012/4/6 Borislav Petkov <bp@...en8.de>:
> Right, what I meant was to add the $(LIBTRACEEVENT): target above to the
> toplevel Makefile so that when you're in the kernel source tree, you do
>
> $ make tools/perf
>
> it has a target $(LIBTRACEEVENT) dependent on it in the toplevel
> Makefile instead of perf's Makefile to avoid duplication. Then, when
> perf is rebuilt, it simply links with this lib. IOW, not have the "make
> -C" call in perf's Makefile but in the toplevel Makefile because other
> tools will want to use libtraceevent.a too and link against it.
>
> Oh well, the toplevel Makefile patches aren't upstream either so we're
> wasting cycles here, I'll fix that up when the times comes.

Yeah let's sort those details out once we have that library merged ;)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ