Building Haiku on Zeta

Can you build a bootable Haiku image on Zeta? I have tried to build Haiku using the Linux build instructions and that failed to build GCC. Additionally, everytime I have tried to pull my files I checked out on Linux or Windows over, I get an error in the configure script saying that there is an invalid token at a line where there shouldn’t be in the shell script (I checked in Vi, it looks clean).

Anyone do this before?

CodeMonekyOverlord wrote:
Can you build a bootable Haiku image on Zeta? I have tried to build Haiku using the Linux build instructions and that failed to build GCC. Additionally, everytime I have tried to pull my files I checked out on Linux or Windows over, I get an error in the configure script saying that there is an invalid token at a line where there shouldn't be in the shell script (I checked in Vi, it looks clean).

Anyone do this before?

You should not need the linux build instructions at all. Zeta is capable of using the 2.95.3 version of GCC posted on bebits - and regular BeOS build instructions can be followed from there:

http://www.haiku-os.org/wiki/index.php?title=Getting_Haiku

So any one building Haiku from Zeta? how did you do that? It says I have an old GCC and I can’t get Olivers to work on Zeta.

I have done it with Zeta 1.21 before - and I was able to use the new GCC 2.95.3 from bebits. Make sure you read the Zeta-specific instructions in the readme for that GCC - it’s a little different when using it on Zeta than it is on R5.

In any case, that was some time ago when I last attempted it - maybe I’ll resurrect the Haiku build environment in my (seldom-used) Zeta partition and try again. The machine I use for building Haiku runs best with R5 because it’s an older machine - so I don’t often use Zeta on it :slight_smile:

The problem was BeIDE and not GCC from Haiku :slight_smile:

Some one knows how to build a specific part of Haiku? like a specific driver?

If you’re building it for Zeta, you would use something like the following:

TARGET_PLATFORM=dano jam <drivername>

But of course - then you’d have to manually copy it.

In many cases, there is already a jam package defined in the Jamfile for many drivers, and you can simply use the jam package target name instead.

For example, building the nvidia driver would be:

TARGET_PLATFORM=dano jam haiku-nvidia-cvs

which will create a .zip containing an install script and necessary parts in the generated folder somewhere (forget exactly where)