public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH] perf: Let O= makes handle relative paths
Date: Mon, 13 Aug 2012 15:02:49 -0300	[thread overview]
Message-ID: <20120813180249.GB6840@infradead.org> (raw)
In-Reply-To: <20120813142909.GC18990@aftab.osrc.amd.com>

Em Mon, Aug 13, 2012 at 04:29:09PM +0200, Borislav Petkov escreveu:
> On Mon, Aug 13, 2012 at 10:23:02AM -0400, Steven Rostedt wrote:
> > On Mon, 2012-08-13 at 15:24 +0200, Borislav Petkov wrote:
> > 
> > > So wouldn't it make sense to call this ABSOLUTE_O or so then?
> > 
> > That's just because you're russian, and are promoting Vodka! ;-)

Before:

[acme@sandy linux]$ rm -rf ../build/perf
[acme@sandy linux]$ make -j8 -C tools/perf/ LIBUNWIND_DIR=/opt/libunwind O=/home/acme/git/build/perf install
/bin/sh: line 0: cd: /home/acme/git/build/perf/: No such file or directory
make: Entering directory `/home/git/linux/tools/perf'
../scripts/Makefile.include:9: *** output directory "/home/acme/git/build/perf/" does not exist.  Stop.
make: Leaving directory `/home/git/linux/tools/perf'
[acme@sandy linux]$

Now:

[acme@sandy linux]$ rm -rf ../build/perf
[acme@sandy linux]$ make -j8 -C tools/perf/ LIBUNWIND_DIR=/opt/libunwind O=/home/acme/git/build/perf install
/bin/sh: line 0: cd: /home/acme/git/build/perf: No such file or directory
make: Entering directory `/home/git/linux/tools/perf'
    GEN perf-archive
    GEN /home/git/linux/tools/perf/python/perf.so
make[1]: Entering directory `/home/git/linux/tools/lib/traceevent'
make[2]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
    * new build flags or cross compiler
    CC /home/git/linux/tools/perf/perf.o
    CC /home/git/linux/tools/perf/builtin-annotate.o
    CC /home/git/linux/tools/perf/builtin-bench.o
    CC /home/git/linux/tools/perf/bench/sched-messaging.o
    CC /home/git/linux/tools/perf/bench/sched-pipe.o

I.e. it should stop if the O= provided directory is not there.

Can you fix this? Avoid vodka while doing it :-P

- Arnaldo

  reply	other threads:[~2012-08-13 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:20 [PATCH] perf: Let O= makes handle relative paths Steven Rostedt
2012-08-13 13:24 ` Borislav Petkov
2012-08-13 14:23   ` Steven Rostedt
2012-08-13 14:29     ` Borislav Petkov
2012-08-13 18:02       ` Arnaldo Carvalho de Melo [this message]
2012-08-15 10:27         ` Borislav Petkov
2012-08-15 13:06           ` Arnaldo Carvalho de Melo
2012-08-15 13:18             ` Borislav Petkov
2012-08-15 14:38               ` Peter Zijlstra
2012-08-15 14:42                 ` Borislav Petkov
2012-08-15 14:59                   ` Arnaldo Carvalho de Melo
2012-08-15 16:39                     ` Borislav Petkov
2012-08-16 16:07                       ` Steven Rostedt
2012-08-16 17:12                         ` Arnaldo Carvalho de Melo
2012-08-21 16:20                       ` [tip:perf/core] perf tools: " tip-bot for Steven Rostedt

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=20120813180249.GB6840@infradead.org \
    --to=acme@infradead.org \
    --cc=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --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