linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
Subject: [RFC 0/4] tools lib traceevent: Install fixes
Date: Mon,  1 Aug 2016 19:41:28 +0200	[thread overview]
Message-ID: <1470073292-18114-1-git-send-email-jolsa@kernel.org> (raw)

hi,
sending traceevent changes to make this lib installable
under rpm spec.

Basically adding support to:
  - install header files
  - install version links

Having this patchset applied over the fedora source,
I could built following rpms:

  kernel-tools-libs
  kernel-tools-libs-devel

with added libtraceevent stuff:

  $ rpm -ql kernel-tools-libs
  /usr/lib64/libcpupower.so.0
  /usr/lib64/libcpupower.so.0.0.0
  /usr/lib64/libtraceevent.so.1
  /usr/lib64/libtraceevent.so.1.1.0

  $ rpm -ql kernel-tools-libs-devel
  /usr/include/cpufreq.h
  /usr/include/traceevent
  /usr/include/traceevent/event-parse.h
  /usr/include/traceevent/event-utils.h
  /usr/include/traceevent/kbuffer.h
  /usr/lib64/libcpupower.so
  /usr/lib64/libtraceevent.a
  /usr/lib64/libtraceevent.so

and could build following ex.c outside the kernel tree:

  $ cat ex.c 
  #include <traceevent/event-parse.h>

  int main(void)
  {
          struct pevent *pevent = pevent_alloc();
          printf("krava %p\n", pevent);
          return 0;
  }
  $ gcc -o ex ex.c -ltraceevent -ldl
  $ ./ex
  krava 0x10c6010
  $


I'll send out fedora rpm build changes once we decide
on this patchset.

Also available in:
  git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
  traceevent/install

thanks,
jirka


---
Jiri Olsa (4):
      tools lib traceevent: Add install_headers target
      tools lib traceevent: Add do_install_mkdir Makefile function
      tools lib traceevent: Rename LIB_FILE to LIB_TARGET
      tools lib traceevent: Add version for traceevent shared object

 tools/lib/traceevent/Makefile | 40 +++++++++++++++++++++++++++-------------
 1 file changed, 27 insertions(+), 13 deletions(-)

             reply	other threads:[~2016-08-01 17:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 17:41 Jiri Olsa [this message]
2016-08-01 17:41 ` [PATCH 1/4] tools lib traceevent: Add install_headers target Jiri Olsa
2016-08-02  2:19   ` Namhyung Kim
2016-08-02  9:30     ` Jiri Olsa
2016-08-01 17:41 ` [PATCH 2/4] tools lib traceevent: Add do_install_mkdir Makefile function Jiri Olsa
2016-08-01 17:41 ` [PATCH 3/4] tools lib traceevent: Rename LIB_FILE to LIB_TARGET Jiri Olsa
2016-08-01 17:41 ` [PATCH 4/4] tools lib traceevent: Add version for traceevent shared object Jiri Olsa
2016-08-02  3:10 ` [RFC 0/4] tools lib traceevent: Install fixes Namhyung Kim
2016-08-02  5:01   ` [PATCH 1/2] tools lib traceevent: Ignore generated library files Namhyung Kim
2016-08-02  5:01     ` [PATCH 2/2] tools lib traceevent: Add str_error_r() Namhyung Kim
2016-08-02 14:27       ` Namhyung Kim
2016-08-04  9:10     ` [tip:perf/urgent] tools lib traceevent: Ignore generated library files tip-bot for Namhyung Kim
2016-08-02  9:31   ` [RFC 0/4] tools lib traceevent: Install fixes Jiri Olsa
2016-08-02 13:48     ` Steven Rostedt
2016-08-02 14:01       ` Jiri Olsa
2016-08-02 14:14         ` Namhyung Kim
2016-08-02 14:18           ` Arnaldo Carvalho de Melo
2016-08-02 14:16         ` Steven Rostedt
2016-08-05 14:13         ` Steven Rostedt
2016-08-05 14:42           ` Arnaldo Carvalho de Melo
2016-08-07 12:56             ` Jiri Olsa
2018-01-19 10:37       ` Jiri Olsa
2018-01-19 15:07         ` Steven Rostedt
2018-01-19 15:15           ` Jiri Olsa
2018-01-26  6:04             ` Namhyung Kim

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=1470073292-18114-1-git-send-email-jolsa@kernel.org \
    --to=jolsa@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).