From: Paolo Bonzini <pbonzini@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures
Date: Thu, 23 Mar 2017 11:33:15 +0100 [thread overview]
Message-ID: <1a35985f-ad4b-c017-b355-51d47aaffa11@redhat.com> (raw)
In-Reply-To: <CAFEAcA-oLDW2F=L3NCdSvrLp_eh3tu9mfKR0mTfZ=3O3dpdKbQ@mail.gmail.com>
On 22/03/2017 14:09, Peter Maydell wrote:
> On 22 March 2017 at 12:51, Alex Bennée <alex.bennee@linaro.org> wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>> ...unfortunately the gcc compile farm mips board (1) is very slow
>>> and (2) has very little disk space free in /tmp, which means that
>>> it can't pass "make check" because for instance tests/test-replication
>>> assumes it can write comparatively large test files to /tmp/...
>>
>> That makes it sound like a mips cross build or mips linux-user powered
>> image would be useful then?
>
> Cross build can't actually run 'make check' and I wouldn't
> trust linux-user to run our test suite. Also, if there's
> no hardware that we can sensibly do make/make check
> on then how much can people really care about QEMU on MIPS?
> (In fact since MIPS supports KVM these days, there really
> ought to be sufficiently capable hardware to work as
> a build system.)
I own a MIPS Creator ci20 board (donated by Imagination Technologies).
I cannot give it a public IP address, but I can try and use it to do
builds every now and then.
Paolo
next prev parent reply other threads:[~2017-03-23 10:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:23 [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Peter Maydell
2017-03-16 15:46 ` Daniel P. Berrange
2017-03-16 15:55 ` Peter Maydell
2017-03-16 16:00 ` Daniel P. Berrange
2017-03-16 16:06 ` Peter Maydell
2017-03-16 16:12 ` Daniel P. Berrange
2017-03-17 9:09 ` Markus Armbruster
2017-03-16 16:52 ` Paolo Bonzini
2017-03-17 9:09 ` Thomas Huth
2017-03-17 10:12 ` Daniel P. Berrange
2017-03-17 10:15 ` Peter Maydell
2017-03-17 10:30 ` Thomas Huth
2017-03-17 10:48 ` Peter Maydell
2017-03-16 18:59 ` Dr. David Alan Gilbert
2017-03-17 9:58 ` Peter Maydell
2017-03-21 17:59 ` Eric Blake
2017-03-16 15:57 ` Gerd Hoffmann
2017-03-16 16:16 ` Daniel P. Berrange
2017-03-16 16:27 ` Peter Maydell
2017-03-16 18:01 ` Peter Maydell
2017-03-16 18:08 ` Daniel P. Berrange
2017-03-22 12:51 ` Alex Bennée
2017-03-22 13:09 ` Peter Maydell
2017-03-22 13:24 ` Thomas Huth
2017-03-23 10:33 ` Paolo Bonzini [this message]
2017-03-23 11:02 ` Peter Maydell
2017-03-24 1:28 ` Richard Henderson
2017-03-24 17:24 ` Peter Maydell
2017-03-22 19:07 ` [Qemu-devel] rawhide gcc failures [was: Proposal for deprecating unsupported host OSes & architecutures] Eric Blake
2017-03-22 19:39 ` Philippe Mathieu-Daudé
2017-03-27 6:36 ` Fam Zheng
2017-03-22 22:33 ` Peter Maydell
2017-03-23 9:25 ` Alex Bennée
2017-03-25 20:49 ` [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Knut Omang
2017-03-25 21:15 ` Peter Maydell
2017-03-26 9:16 ` Knut Omang
2017-03-27 16:32 ` Peter Maydell
2017-03-28 18:34 ` Knut Omang
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=1a35985f-ad4b-c017-b355-51d47aaffa11@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--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).