Vagrant boxes for Haiku nightly!

I got Haiku nightly running in Vagrant, in order to make it easier to setup build bots and compile and test software for Haiku from different host environments.


Packer source:

There were quite a few little shims and tricks needed to integrate Haiku nightly with essential Vagrant features; dive into the Packer source! In the future, we can promote some of these workarounds to the Vagrant Haiku guest plugin (currently written for Haiku alpha 4), and trim off other workarounds as Haiku progresses.

For my purposes, I just wanted to see if a C project could be structured to cross-compile between different target kernels, and Haiku makes lucky number 13! I’ve added a Haiku amd64 demo to my tonixxx project, and may one day add Haiku x86 back, if x86 gets gcc 4.7 support, or I decide to backport my C code to C89, ha.


There is a gcc 5.4 shipped with x86 releases. It’s just named gcc-x86 instead of gcc. Or you can use “setarch x86” to open a shell where it is the default gcc (with a few environment variables set properly to help buildsystems)

1 Like

Thank you for the info! In truth, llvm_x86_clang is installed as well, and perhaps fails to update cc, resulting in cmake finding the older gcc 2 compiler :confused:

Any package with _x86 puts all its commands in the secondary arch bin folder, so setarch x86 will also make clang available.


Thank you for your posts. Love seeing Haiku being put through its paces.