From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1715203 <1715203@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1715203] [NEW] Maintain Haiku support
Date: Tue, 5 Sep 2017 19:08:44 +0100 [thread overview]
Message-ID: <CAFEAcA--Twu0_+O3VD90bPs3CXQqgugNq_x+hUCv_gF9zYEdYA@mail.gmail.com> (raw)
In-Reply-To: <150463414707.19543.9931062189110648888.malonedeb@chaenomeles.canonical.com>
On 5 September 2017 at 18:55, kallisti5 <1715203@bugs.launchpad.net> wrote:
> It was pointed out that the 2.10 release notes are pushing to drop Haiku
> support. The qemu port is currently working as-is under Haiku.
>
> Was there a reason this was recommended? Is there anything Haiku can do
> to keep it from being dropped?
Basically we don't want to try to support host systems where we
have no access to hardware that will let us compile and run
the test suite, and where there's nobody interacting with us
upstream to help fix issues that are Haiku related.
If there's genuinely a community of Haiku QEMU users out there
who want to help us maintain the support in the QEMU codebase that's
great. What we don't want is to be carrying around code we can't
test and where we don't seem to have anybody using it. (For instance
we're about to drop support for AIX...)
> We're working on a docker container to cross-compile rust-lang for
> Haiku, could this be of some use to qemu when complete?
Cross-compilation won't let us run the test suite.
thanks
-- PMM
next prev parent reply other threads:[~2017-09-05 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 17:55 [Qemu-devel] [Bug 1715203] [NEW] Maintain Haiku support kallisti5
2017-09-05 18:08 ` Peter Maydell [this message]
2017-09-05 18:14 ` [Qemu-devel] [Bug 1715203] " kallisti5
2017-09-05 18:25 ` Peter Maydell
2017-09-05 19:00 ` kallisti5
2017-09-08 1:09 ` kallisti5
2020-09-05 9:43 ` Thomas Huth
2020-09-05 12:03 ` kallisti5
2020-09-05 14:46 ` kallisti5
2020-09-05 14:48 ` kallisti5
2020-09-05 15:19 ` kallisti5
2020-09-05 16:18 ` Thomas Huth
2020-09-06 14:45 ` kallisti5
2020-11-17 18:33 ` Thomas Huth
2021-04-30 9:14 ` Thomas Huth
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--Twu0_+O3VD90bPs3CXQqgugNq_x+hUCv_gF9zYEdYA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=1715203@bugs.launchpad.net \
--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).