[Bug 1715203] Re: Maintain Haiku support

[kallisti5]

$ ./haiku.x86_64 --verbose --image /tmp/haiku.img uname
Haiku

./haiku.x86_64 --verbose --image /tmp/haiku.img "gcc -v"
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/8.3.0/lto-wrapper
Target: x86_64-unknown-haiku
Configured with: /sources/gcc-8.3.0/configure --build=x86_64-unknown-haiku 
--prefix=/packages/gcc-8.3.0_2019_05_24-7/.self/develop/tools 
--libexecdir=/packages/gcc-8.3.0_2019_05_24-7/.self/develop/tools/lib 
--mandir=/packages/gcc-8.3.0_2019_05_24-7/.self/documentation/man 
--docdir=/packages/gcc-8.3.0_2019_05_24-7/.self/documentation/packages/gcc 
--enable-threads=posix --disable-nls --enable-shared --with-gnu-ld 
--with-gnu-as --enable-version-specific-runtime-libs 
--enable-languages=c,c++,fortran,objc --enable-lto --enable-frame-pointer 
--with-pkgversion=2019_05_24 --enable-__cxa-atexit --with-system-zlib 
--enable-checking=release --with-bug-url=http://dev.haiku-os.org/ 
--with-default-libstdcxx-abi=gcc4-compatible --enable-libssp --disable-multilib
Thread model: posix
gcc version 8.3.0 (2019_05_24)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715203

Title:
  Maintain Haiku support

Status in QEMU:
  Incomplete

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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1715203/+subscriptions