qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
	Stefan Weil <sw@weilnetz.de>,
	Igor Mitsyanko <i.mitsyanko@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] configure: fix ALSA configure test
Date: Mon, 23 Jul 2012 18:45:43 +0100	[thread overview]
Message-ID: <CAFEAcA-UC5Pmt-oMJx0okH2F6EWNY5XDmURq2EqXnPJuOBAL0w@mail.gmail.com> (raw)
In-Reply-To: <CAAu8pHvJVj=cU-q9gjrGinPT97O+60L4vipzYMVeWy+T2o3cuA@mail.gmail.com>

On 23 July 2012 18:40, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Tue, Jul 17, 2012 at 7:28 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> The trouble is that the warnings and errors here don't cause the
>> build to fail noisily; that's a big distinction IMHO.
>> I suppose we could make compile_prog do something like:
>>  * run the compile test
>
> Unfortunately that would break cross compiling.

Sorry, that was slightly unclear phrasing. By "run the test"
I meant "do the check that we can compile the test code"
"run the binary produced". This series won't break cross
compiling.

-- PMM

  reply	other threads:[~2012-07-23 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 17:34 [Qemu-devel] [PATCH] configure: fix ALSA configure test Igor Mitsyanko
2012-07-17 18:03 ` Igor Mitsyanko
2012-07-17 18:32   ` Stefan Weil
2012-07-17 18:46     ` Peter Maydell
2012-07-17 19:24       ` Stefan Weil
2012-07-17 19:28         ` Peter Maydell
2012-07-17 19:42           ` Stefan Weil
2012-07-21  9:37           ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-07-23 17:40           ` [Qemu-devel] " Blue Swirl
2012-07-23 17:45             ` Peter Maydell [this message]
2012-07-23 19:32               ` Peter Maydell

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=CAFEAcA-UC5Pmt-oMJx0okH2F6EWNY5XDmURq2EqXnPJuOBAL0w@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=i.mitsyanko@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).