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>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtraceevent: fix header installation
Date: Thu, 14 Nov 2019 20:30:30 -0300	[thread overview]
Message-ID: <76775DFB-79CB-4B85-86CE-EB9406976E9D@kernel.org> (raw)
In-Reply-To: <20191114174022.62c8259e@gandalf.local.home>

On November 14, 2019 7:40:22 PM GMT-03:00, Steven Rostedt <rostedt@goodmis.org> wrote:
>
>Arnaldo,
>
>Can you take this?

Sure

>
>Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
>-- Steve
>
>
>On Thu, 14 Nov 2019 13:37:19 +0000
>Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
>
>> When we passed some location in DESTDIR, install_headers called
>> do_install with DESTDIR as part of the second argument. But
>do_install
>> is again using '$(DESTDIR_SQ)$2', so as a result the headers were
>> installed in a location $DESTDIR/$DESTDIR. In my testing I passed
>> DESTDIR=/home/sudip/test and the headers were installed in:
>> /home/sudip/test/home/sudip/test/usr/include/traceevent.
>> Lets remove DESTDIR from the second argument of do_install so that
>the
>> headers are installed in the correct location.
>> 
>> Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
>> ---
>> 
>> Hi Steve,
>> sent this earlier as an attachment to an email thread, not sure if
>you
>> saw it, so sending it now properly.
>> The other problem with the pkgconfig, I guess we can live with that
>for
>> now as that folder is given by pc_path.
>> 
>>  tools/lib/traceevent/Makefile | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>> 
>> diff --git a/tools/lib/traceevent/Makefile
>b/tools/lib/traceevent/Makefile
>> index 5315f3787f8d..cbb429f55062 100644
>> --- a/tools/lib/traceevent/Makefile
>> +++ b/tools/lib/traceevent/Makefile
>> @@ -232,10 +232,10 @@ install_pkgconfig:
>>  
>>  install_headers:
>>  	$(call QUIET_INSTALL, headers) \
>> -		$(call do_install,event-parse.h,$(DESTDIR)$(includedir_SQ),644); \
>> -		$(call do_install,event-utils.h,$(DESTDIR)$(includedir_SQ),644); \
>> -		$(call do_install,trace-seq.h,$(DESTDIR)$(includedir_SQ),644); \
>> -		$(call do_install,kbuffer.h,$(DESTDIR)$(includedir_SQ),644)
>> +		$(call do_install,event-parse.h,$(includedir_SQ),644); \
>> +		$(call do_install,event-utils.h,$(includedir_SQ),644); \
>> +		$(call do_install,trace-seq.h,$(includedir_SQ),644); \
>> +		$(call do_install,kbuffer.h,$(includedir_SQ),644)
>>  
>>  install: install_lib
>>  


  reply	other threads:[~2019-11-14 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 13:37 [PATCH] libtraceevent: fix header installation Sudip Mukherjee
2019-11-14 22:40 ` Steven Rostedt
2019-11-14 23:30   ` Arnaldo Carvalho de Melo [this message]
2019-11-21 14:40   ` Arnaldo Carvalho de Melo
2019-11-23  8:15 ` [tip: perf/core] libtraceevent: Fix " 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=76775DFB-79CB-4B85-86CE-EB9406976E9D@kernel.org \
    --to=arnaldo.melo@gmail.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).