From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Sean Bruno <sbruno@freebsd.org>, Brad Smith <brad@comstyle.com>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-2.7] pc-bios/optionrom: Fix OpenBSD build with better detection of linker emulation
Date: Tue, 9 Aug 2016 14:15:43 +0100 [thread overview]
Message-ID: <CAFEAcA8iWWi077dckqsFvoMSkDehwa6SynNHHRM6cEPXLfz11A@mail.gmail.com> (raw)
In-Reply-To: <8fe72834-047d-4d1b-a004-4f44d8163e4d@redhat.com>
On 9 August 2016 at 14:12, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 08/08/2016 19:12, Peter Maydell wrote:
>> PS: if you would like your BSD flavour promoted to "we don't
>> merge changes that break the build on it" I would need to
>> have ssh access to a machine I can run builds and tests on.
>> (Unfortunately the only BSD in the gcc compile farm is an
>> ancient NetBSD.)
>
> For the purpose of "not breaking the build", having a docker image for a
> cross compiler would also be enough.
My requirement here is largely that I personally don't have
to expend any effort on admining and maintaining BSD related
build setups. I also think that setups that let you run "make
check" are much more valuable than cross-compile setups that
don't.
thanks
-- PMM
next prev parent reply other threads:[~2016-08-09 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:11 [Qemu-devel] [PATCH for-2.7] pc-bios/optionrom: Fix OpenBSD build with better detection of linker emulation Peter Maydell
2016-08-08 17:12 ` Peter Maydell
2016-08-09 13:12 ` Paolo Bonzini
2016-08-09 13:15 ` Peter Maydell [this message]
2016-08-08 18:05 ` Sean Bruno
2016-08-10 23:42 ` Brad Smith
2016-08-11 9:24 ` Peter Maydell
2016-08-11 0:28 ` Brad Smith
2016-08-15 17:26 ` Peter Maydell
2016-08-15 18:52 ` Brad Smith
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=CAFEAcA8iWWi077dckqsFvoMSkDehwa6SynNHHRM6cEPXLfz11A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=brad@comstyle.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sbruno@freebsd.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).