Originally Posted by
umccullough
The problem is: Haiku is currently pre-alpha and doesn't have any build tools installed by default. The pending Alpha release will have this support soon.
Parallels users have succeeded in running it by using the ImgTool to fix the disk size (not sure why this is - apparently Parallels can't use the raw disk image as it is). VMWare is actually much easier to use and demonstrates excellent performance for Haiku.
BeOS R5 is completely installable and has development tools - but lacks a lot of modern drivers (BeOS Max Edition V4 b1 is the best choice)
Zeta supports a lot of modern hardware, but is commercial and now defunct (like BeOS was).
Many dedicated Haiku testers have been able to load the BeOS R5 development tools onto their Haiku installs and compile working software - but software compiled *ON* BeOS is upward binary compatible with both Haiku and Zeta - so this is where I would focus efforts in order to support all 3 OSes with a single binary release.
Another interesting detail is that BeOS and Zeta use an "updated" GCC 2.95.3 still because GCC3 and newer have broken ABI compatibility with C++ binaries generated with GCC2. Haiku can be also compiled with GCC4, but a GCC4 binary for Haiku will not currently run on a GCC2 version of Haiku which is required to retain binary compatibility with BeOS R5 and Zeta.
If it would help, I can probably get you a BeOS R5 vmware or QEMU image complete with build tools. I can probably also do the same with Haiku.