From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
QEMU Developer <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call for 2017-03-14
Date: Tue, 14 Mar 2017 16:01:14 +0000 [thread overview]
Message-ID: <20170314160113.GM2445@work-vm> (raw)
In-Reply-To: <87wpbstesf.fsf@secure.mitica>
* Juan Quintela (quintela@redhat.com) wrote:
> Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 14 March 2017 at 09:13, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >> On Mon, Mar 13, 2017 at 11:02:01AM +0100, Peter Maydell wrote:
> >> The minimum requirements for the new language:
> >> 1. Does it support the host operating systems that QEMU runs on?
> >> 2. Does it support the host architectures that QEMU runs on?
> >
> > Speaking of this, I was thinking that we should introduce
> > a rule that for any host OS/arch we support we must have
> > a build machine so we can at least do a compile test.
> > For instance if you believe configure we support Solaris
> > and AIX, but I bet they're bit-rotting. The ia64 backend
> > has to be a strong candidate for being dumped too.
> > Demanding "system we can test on or we drop support"
> > would let us more clearly see what we're actually running
> > on and avoid unnecessarily ruling things out because they
> > don't support Itanium or AIX...
>
> YES, YES and YES.
>
> I demand an osX build machine NOW!!!! Remote access is ok.
>
> Now more seriously, I can (relatively easy) compile test my pull
> requests with:
> - linux x86 (latest fedora, but I can get an older one if needed)
> - linux x86_64 (latest fedor,, but the same)
> - mingw64 32bit (latest fedora, but here I have the problem that Peter
> uses a different crosscompiler than me)
> - mingw64 32bit (the same)
>
> But for the rest, I need to wait that somebody told me that it breaks
> the build. Normally it is things like size_t is 32bit instead of 64bit
> or some stupid things like that, that are trivial to fix if I can
> compile there before doing the pull submission.
I also do a FreeBSD VM, and grab an aarch64 and/or PPC bigendian host
to test on.
(I could grab an ia64 host, but I don't think I could find anything
to install on it that would be new enough for the rest of our build
requirements).
Dave
> Later, Juan.
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-03-14 16:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:45 [Qemu-devel] KVM call for 2017-03-14 Juan Quintela
2017-03-13 10:02 ` Peter Maydell
2017-03-13 12:50 ` Alex Bennée
2017-03-13 14:12 ` Juan Quintela
2017-03-13 14:17 ` Peter Maydell
2017-03-14 8:03 ` Stefan Hajnoczi
2017-03-14 8:13 ` Stefan Hajnoczi
2017-03-14 8:37 ` Peter Maydell
2017-03-14 8:59 ` Juan Quintela
2017-03-14 10:56 ` Peter Maydell
2017-03-15 8:39 ` Christian Borntraeger
2017-03-15 10:29 ` Greg Kurz
2017-03-15 11:25 ` Laurent Vivier
2017-03-15 16:35 ` Greg Kurz
2017-03-14 16:01 ` Dr. David Alan Gilbert [this message]
2017-03-14 16:20 ` Daniel P. Berrange
2017-03-14 16:54 ` [Qemu-devel] Obsolete QEMU host environments (was: Re: KVM call for 2017-03-14) Thomas Huth
2017-03-14 17:07 ` Peter Maydell
2017-03-14 21:09 ` [Qemu-devel] Obsolete QEMU host environments Richard Henderson
2017-03-15 9:40 ` Daniel P. Berrange
2017-03-15 10:02 ` Thomas Huth
2017-03-15 15:46 ` Aurelien Jarno
2017-03-14 17:14 ` [Qemu-devel] KVM call for 2017-03-14 Paolo Bonzini
2017-03-14 17:18 ` Peter Maydell
2017-03-14 17:29 ` Dr. David Alan Gilbert
2017-03-15 8:30 ` Gerd Hoffmann
2017-03-14 9:33 ` Markus Armbruster
2017-03-14 8:53 ` Juan Quintela
2017-03-14 10:39 ` Peter Maydell
2017-03-14 10:44 ` Paolo Bonzini
2017-03-14 9:24 ` Thomas Huth
2017-03-14 10:13 ` Kevin Wolf
2017-03-14 12:20 ` Markus Armbruster
2017-03-14 12:35 ` Kevin Wolf
2017-03-14 10: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=20170314160113.GM2445@work-vm \
--to=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
/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).