[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Proposal for deprecating unsupported host OSes & architecut

From: Peter Maydell
Subject: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures
Date: Thu, 16 Mar 2017 15:23:45 +0000

OK, here's a concrete proposal for deprecating/dropping out of
date host OS and architecture support.

We'll put this in the ChangeLog 'Future incompatible changes'
* Removal of support for untested host OS and architectures:

The QEMU Project intends to drop support in a future release for any
host OS or architecture which we do not have access to a build and test
machine for. This affects the following host OSes:
 * Native CYGWIN building
 * GNU/kFreeBSD
 * FreeBSD
 * DragonFly BSD
 * NetBSD
 * OpenBSD
 * Solaris
 * AIX
 * Haiku
and the following host CPU architectures:
 * ia64
 * sparc

Specifically, if we do not have a build and test system available
to us by the time we release QEMU 2.10, we will remove support in the
release that follows 2.10.

I'm not sure here if we want to just have this as a bald list,
or to have some kind of two tier setup with OSes we expect to
dump in one tier and OSes where we're really trolling for a build
machine in the other tier (the "unlikely to dump" category would
get most of the BSD variants in it). Putting out a changelog
that says "we're gonna drop all the BSDs" seems like it might
produce a lot of yelling?

Should "native CYGWIN" be in the drop list? I only test
mingw cross compile, but configure has a separate section for
CYGWIN in its $targetos case statement.

It would also not be too difficult to make configure warn when it
is run on the deprecated OS or architecture, so we should probably
sneak that into 2.9.

(Technically right this instant 'mips' and 's390' would be in the
'dump' list, since I don't personally have access yet. But we have
a plan for s390, and it turns out there is a mips machine in the
gcc compile farm which I'm just checking out.)

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]