qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Cheung <mcheung63@hotmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] This is an out of tree build but your source tree
Date: Mon, 20 May 2013 08:17:33 +0200	[thread overview]
Message-ID: <CAJSP0QWFpXyA-QMV8oJy44ds8XwyYVy9QqJupzPED9o2qa5=uQ@mail.gmail.com> (raw)
In-Reply-To: <BAY147-W318BCABBEC1D56E276335BB5AF0@phx.gbl>

On Mon, May 20, 2013 at 4:33 AM, Peter Cheung <mcheung63@hotmail.com> wrote:
> /Users/peter/workspace/qemu_latest>make
> Makefile:16: *** This is an out of tree build but your source tree
> (/Users/peter/workspace/qemu_latest) seems to have been used for an in-tree
> build. You can fix this by running "make distclean && rm -rf *-linux-user
> *-softmmu" in your source tree.  Stop.
>
> even i run "make distclean && rm -rf *-linux-user *-softmmu", it doesn't
> help.

Are you trying to do an out-of-tree build?  If yes, run the distclean
command in the _source tree_ and not in your out-of-tree directory.

If you are not trying to do an out-of-tree build then maybe the
Makefile is buggy here on Mac OS X:
ifneq ($(realpath $(SRC_PATH)),$(realpath .))

Please add $(realpath $(SRC_PATH)) and $(realpath .) to the error
message.  That way you can confirm whether the path matching makes
sense.

Stefan

  reply	other threads:[~2013-05-20  6:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20  2:33 [Qemu-devel] This is an out of tree build but your source tree Peter Cheung
2013-05-20  6:17 ` Stefan Hajnoczi [this message]
2013-05-20  8:11   ` Peter Maydell
2013-05-20  8:11     ` Peter Maydell
2013-05-21  6:30   ` Peter Cheung
2013-05-20 15:59 ` Andreas Färber
2013-05-20 21:51   ` Peter Crosthwaite
2013-05-21  6:32   ` Peter Cheung

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='CAJSP0QWFpXyA-QMV8oJy44ds8XwyYVy9QqJupzPED9o2qa5=uQ@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=mcheung63@hotmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).