linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	arnaldo.melo@gmail.com, linux-kernel@vger.kernel.org,
	linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtraceevent: allow custom libdir path
Date: Thu, 12 Dec 2019 14:55:31 -0300	[thread overview]
Message-ID: <20191212175531.GG13965@kernel.org> (raw)
In-Reply-To: <20191212111900.3f46e033@gandalf.local.home>

Em Thu, Dec 12, 2019 at 11:19:00AM -0500, Steven Rostedt escreveu:
> 
> Arnaldo,
> 
> Can you pull this patch in?
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

Sure, applied.

- Arnaldo
 
> -- Steve
> 
> 
> On Sat,  7 Dec 2019 11:14:40 +0000
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
> 
> > When I use prefix=/usr and try to install libtraceevent in my laptop it
> > tries to install in /usr/lib64. I am not having any folder as /usr/lib64
> > and also the debian policy doesnot allow installing in /usr/lib64. It
> > should be in /usr/lib/x86_64-linux-gnu/.
> > 
> > Quote: No package for a 64 bit architecture may install files in
> > 	/usr/lib64/ or in a subdirectory of it.
> > ref: https://www.debian.org/doc/debian-policy/ch-opersys.html
> > 
> > Make it more flexible by allowing to mention libdir_relative while
> > installing so that distros can mention the path according to their policy
> > or use the default one.
> > 
> > Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> > ---
> > 
> > Hi Steve,
> > 
> > And yet another one (hopefully the final one for now). I know I missed
> > the merge window, but your Ack should be ok.
> > 
> >  tools/lib/traceevent/Makefile         | 5 +++--
> >  tools/lib/traceevent/plugins/Makefile | 5 +++--
> >  2 files changed, 6 insertions(+), 4 deletions(-)
> > 
> > diff --git a/tools/lib/traceevent/Makefile b/tools/lib/traceevent/Makefile
> > index c5a03356a999..7e2450ddd7e1 100644
> > --- a/tools/lib/traceevent/Makefile
> > +++ b/tools/lib/traceevent/Makefile
> > @@ -39,11 +39,12 @@ DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))'
> >  
> >  LP64 := $(shell echo __LP64__ | ${CC} ${CFLAGS} -E -x c - | tail -n 1)
> >  ifeq ($(LP64), 1)
> > -  libdir_relative = lib64
> > +  libdir_relative_temp = lib64
> >  else
> > -  libdir_relative = lib
> > +  libdir_relative_temp = lib
> >  endif
> >  
> > +libdir_relative ?= $(libdir_relative_temp)
> >  prefix ?= /usr/local
> >  libdir = $(prefix)/$(libdir_relative)
> >  man_dir = $(prefix)/share/man
> > diff --git a/tools/lib/traceevent/plugins/Makefile b/tools/lib/traceevent/plugins/Makefile
> > index f440989fa55e..edb046151305 100644
> > --- a/tools/lib/traceevent/plugins/Makefile
> > +++ b/tools/lib/traceevent/plugins/Makefile
> > @@ -32,11 +32,12 @@ DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))'
> >  
> >  LP64 := $(shell echo __LP64__ | ${CC} ${CFLAGS} -E -x c - | tail -n 1)
> >  ifeq ($(LP64), 1)
> > -  libdir_relative = lib64
> > +  libdir_relative_tmp = lib64
> >  else
> > -  libdir_relative = lib
> > +  libdir_relative_tmp = lib
> >  endif
> >  
> > +libdir_relative ?= $(libdir_relative_tmp)
> >  prefix ?= /usr/local
> >  libdir = $(prefix)/$(libdir_relative)
> >  

-- 

- Arnaldo

  reply	other threads:[~2019-12-12 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 11:14 [PATCH] libtraceevent: allow custom libdir path Sudip Mukherjee
2019-12-12 16:19 ` Steven Rostedt
2019-12-12 17:55   ` Arnaldo Carvalho de Melo [this message]
2019-12-17 11:31 ` [tip: perf/urgent] libtraceevent: Allow " tip-bot2 for Sudip Mukherjee

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=20191212175531.GG13965@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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).