Maintain Haiku support
Bug #1715203 reported by
kallisti5
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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?
We're working on a docker container to cross-compile rust-lang for Haiku, could this be of some use to qemu when complete?
Changed in qemu: | |
status: | Incomplete → Confirmed |
Changed in qemu: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
On 5 September 2017 at 18:55, kallisti5 <email address hidden> 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