All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@sysprog.at>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Kusanagi Kouichi <slash@ac.auone-net.jp>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix build error on read only source.
Date: Thu, 19 Aug 2010 11:02:10 +0200	[thread overview]
Message-ID: <1282208530.10440.3.camel@thorin> (raw)
In-Reply-To: <20100818190959.GI9410@ghostprotocols.net>

On Mit, 2010-08-18 at 16:09 -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Aug 18, 2010 at 02:01:58PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Aug 18, 2010 at 01:56:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Wed, Aug 18, 2010 at 04:27:45PM +0200, Peter Zijlstra escreveu:
> > > > On Wed, 2010-08-18 at 11:16 -0300, Arnaldo Carvalho de Melo wrote:
> > > > > rm -rf ~/build
> > > > > make O=~/build
> > > > > 
> > > > > and have everything work? Saving some keystrokes 8)
> > > > 
> > > > The turn side is that if you typo the output dir you'll probably not
> > > > ever find it again.. and you could have typed: rm -rf ~/build/* instead.

Well, usually interactive shells have a history. But since the other
Makefiles also expect existing destination top directory ...

> > > Not something I'll argue too much :)
> 
> Ok, here it is, stolen directly from the toplevel kernel Makefile, will push to

ACK, it's the same problem so the same solution is the best.

> Ingo today:
> 
> [acme@emilia linux-2.6-tip]$ rm -rf ~/git/build/perf
> [acme@emilia linux-2.6-tip]$ make -j9 O=~/git/build/perf -C tools/perf
> /bin/sh: line 0: cd: /home/acme/git/build/perf/: No such file or directory

ACK, that should make the "problem" pretty clear.

	Bernd
-- 
mobile: +43 664 4416156              http://www.sysprog.at/
    Linux Software Development, Consulting and Services


  reply	other threads:[~2010-08-19  9:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 18:18 [PATCH] perf tools: Fix build error on read only source Arnaldo Carvalho de Melo
2010-08-18 12:37 ` Kusanagi Kouichi
2010-08-18 12:40   ` Peter Zijlstra
2010-08-18 14:16     ` Arnaldo Carvalho de Melo
2010-08-18 14:27       ` Peter Zijlstra
2010-08-18 16:56         ` Arnaldo Carvalho de Melo
2010-08-18 17:01           ` Arnaldo Carvalho de Melo
2010-08-18 19:09             ` Arnaldo Carvalho de Melo
2010-08-19  9:02               ` Bernd Petrovitsch [this message]
2010-08-18 14:14   ` Arnaldo Carvalho de Melo
2010-08-18 15:25     ` Bernd Petrovitsch
2010-08-18 17:19       ` Arnaldo Carvalho de Melo
2010-08-19 10:31         ` Bernd Petrovitsch
2010-08-19 14:13           ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2010-08-16 12:40 Kusanagi Kouichi
2010-08-16 15:24 ` Arnaldo Carvalho de Melo
2010-08-17 12:57   ` Kusanagi Kouichi
2010-08-17 14:08   ` Kusanagi Kouichi
2010-08-17 14:17     ` Arnaldo Carvalho de Melo

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=1282208530.10440.3.camel@thorin \
    --to=bernd@sysprog.at \
    --cc=acme@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=slash@ac.auone-net.jp \
    /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.