public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH regression 4.0 -> 4.1] tools perf: Fix build breakage if prefix= is specified
Date: Thu, 18 Jun 2015 16:07:56 -0600	[thread overview]
Message-ID: <5583413C.1040802@gmail.com> (raw)
In-Reply-To: <20150618203935.GA4806@wunner.de>

On 6/18/15 2:39 PM, Lukas Wunner wrote:
> So the prefix parameter should have no effect at all in your case,
> no matter to what you set it.

It does:

rpmbuild -bb --define="_prefix /tmp/junk" SPECS/perf.spec

...
+ make -s -C tools/perf V=1 WERROR=0 NO_LIBUNWIND=1 
HAVE_CPLUS_DEMANGLE=1 NO_GTK2=1 NO_STRLCPY=1 NO_BIONIC=1 
prefix=/tmp/junk DESTDIR=/root/rpmbuild/BUILDROOT/perf-4.1.rc6-1.x86_64 all

...

Note that prefix=/tmp/junk when tools/perf/Makefile gets invoked.

[root@f21-vbox rpmbuild]# rpm -qvlp 
/root/rpmbuild/RPMS/x86_64/perf-4.1.rc6-1.x86_64.rpm | grep bin/perf
-rwxr-xr-x    2 root    root                  2382176 Jun 18 13:10 
/tmp/junk/bin/perf



  parent reply	other threads:[~2015-06-18 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201506181332.t5IDWuUq027242@int-mx13.intmail.prod.int.phx2.redhat.com>
2015-06-18 19:29 ` [PATCH regression 4.0 -> 4.1] tools perf: Fix build breakage if prefix= is specified Jiri Olsa
2015-06-18 19:59   ` Lukas Wunner
2015-06-18 20:26     ` David Ahern
2015-06-18 20:39       ` Lukas Wunner
2015-06-18 21:51         ` Jiri Olsa
2015-06-18 22:07         ` David Ahern [this message]
2015-06-18 22:17         ` Jiri Olsa
2015-06-19 11:54           ` Lukas Wunner
2015-06-19 14:19             ` Arnaldo Carvalho de Melo
2015-06-18 21:52 ` Jiri Olsa

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=5583413C.1040802@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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