All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
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 17:59:12 +0200	[thread overview]
Message-ID: <519A4850.2030008@suse.de> (raw)
In-Reply-To: <BAY147-W318BCABBEC1D56E276335BB5AF0@phx.gbl>

Hi,

Am 20.05.2013 04:33, schrieb Peter Cheung:
> Hi all
>     I have this problem in my Mac
> 
> /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.

If nothing else works, commit all your changes to your source tree and
run in the source directory `rm -rf *` (this should delete all
non-hidden files, leaving .git intact) followed by `git reset --hard` to
restore all files from the index.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2013-05-20 15:59 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
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 [this message]
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=519A4850.2030008@suse.de \
    --to=afaerber@suse.de \
    --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 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.