All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Robert Richter <rric@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
	hpa@zytor.com, linux-kernel@vger.kernel.org, jolsa@redhat.com,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix 'make tools/perf'
Date: Thu, 18 Jul 2013 13:19:13 -0300	[thread overview]
Message-ID: <20130718161913.GA2288@ghostprotocols.net> (raw)
In-Reply-To: <20130718121924.GL8731@rric.localhost>

Em Thu, Jul 18, 2013 at 02:19:24PM +0200, Robert Richter escreveu:
> Arnaldo,
> 
> I noticed you applied the patch to acme/perf/core, but it should be
> instead in urgent since mainline is broken.

I did it because there are alternative ways to build the tools that
don't require this fix, i.e. this is not _strictly_ needed to build the
tools.

What do you guys think: a case like this always needs to go to the
current release candidate? Ingo?

- Arnaldo
 
> On 17.07.13 18:10:51, Robert Richter wrote:
> > On 17.07.13 17:40:01, Borislav Petkov wrote:
> > > On Wed, Jul 17, 2013 at 12:31:18PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Humm, probably it will look at the top level 'install' target? There
> > > > was some discussion about this, right? Can you refresh my mind?
> 
> Now tested with:
> 
>  make O=... DESTDIR=... tools/perf
>  make O=... DESTDIR=... tools/perf_install
>  make O=... DESTDIR=... -C tools/ perf
>  make O=... DESTDIR=... -C tools/ perf_install
>  make O=... DESTDIR=... -C tools/perf
>  make O=... DESTDIR=... -C tools/perf install
>  make tools/perf
>  make DESTDIR=... tools/perf_install
>  make -C tools/ perf
>  make -C tools/ DESTDIR=... perf_install
>  make -C tools/perf
>  make -C tools/perf DESTDIR=... install
> 
> No issues noticed, accept that doc is built when running the 'install'
> target, not 'all'.
> 
> Will look at this.
> 
> We also should remove dependencies from install targets that trigger a
> rebuild since 'make install' is run as root. I had a conversation with
> Linus about this for building the arm kernel, but the same applies
> also for perf tools. I don't have the time for changing this now, but
> maybe in some weeks or so.
> 
> Thanks,
> 
> -Robert

  reply	other threads:[~2013-07-18 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 15:22 [PATCH] perf tools: Fix build errors with O and DESTDIR make vars set Robert Richter
2013-07-12  8:49 ` [tip:perf/urgent] " tip-bot for Robert Richter
2013-07-12  9:39   ` Robert Richter
2013-07-16 14:50     ` [PATCH] perf tools: Fix 'make tools/perf' Robert Richter
2013-07-17 15:31       ` Arnaldo Carvalho de Melo
2013-07-17 15:40         ` Borislav Petkov
2013-07-17 16:10           ` Robert Richter
2013-07-18 12:19             ` Robert Richter
2013-07-18 16:19               ` Arnaldo Carvalho de Melo [this message]
2013-07-18 16:47                 ` Robert Richter
2013-07-18 16:41               ` [PATCH] perf tools: Build docs with 'make all' Robert Richter
2013-07-19  7:53       ` [tip:perf/core] perf tools: Fix 'make tools/perf' tip-bot for Robert Richter

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=20130718161913.GA2288@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rric@kernel.org \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.