qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH v2] Force object directory use
Date: Thu, 18 Nov 2010 00:51:48 +0100	[thread overview]
Message-ID: <4CE46A94.6040007@redhat.com> (raw)
In-Reply-To: <AANLkTikHJJ4hSqxPny5K34McMVKz2Z0HNpTk2uL7pSLG@mail.gmail.com>

On 11/18/2010 12:05 AM, Peter Maydell wrote:
>> >  It may be unified but it's pretty much unlike every other
>> >  build system I've ever seen.
> If you want another approach you could do what glibc does (IIRC),
> which is to just give an error message if you invoke configure in
> the source directory suggesting that you run it in a separate build
> directory.

Yes, that would be better.

Paolo

  reply	other threads:[~2010-11-17 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 19:15 [Qemu-devel] [PATCH v2] Force object directory use Blue Swirl
2010-11-17 20:00 ` [Qemu-devel] " Paolo Bonzini
2010-11-17 20:08   ` Blue Swirl
2010-11-17 22:39     ` Paolo Bonzini
2010-11-17 23:05       ` Peter Maydell
2010-11-17 23:51         ` Paolo Bonzini [this message]
2010-11-17 23:57       ` Anthony Liguori

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=4CE46A94.6040007@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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).