[haiku-development] Re: Error building in ZETA
- From: "Stephan Assmus" <superstippi@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 04 Sep 2008 00:07:58 +0200
Hi,
> So far, I've been using R5 on my dual P3 650 for my Haiku development
> (development? WHAT development?) but I got tired of its slowness (why,
> oh why is GCC single threaded?). Neither ZETA nor R5 run on my new dual
> core, so I collected some spare parts and resurrected my trusty Athlon,
> which can run ZETA. I'll put it away again when Haiku will be stable
> enough on the dual core, but for now, I'm happy my KVM switch has four
> ports...
It depends a bit on what you are doing and want to use Haiku for, but I would
recommend installing a Linux on your dual core with a build environment to
build Haiku. Then you make two partitions for Haiku, one where you can create a
Haiku installation from Linux and one for holding more persistent data within
Haiku. I too have a computer (notebook) that only runs Haiku and no BeOS/ZETA
and in the past weeks, I was on the go a lot. So I was forced to use Haiku
exclusively to develop stuff. (I don't really like doing serious work in Linux,
somehow I don't feel at home and productive there.) Haiku definitely survives a
day of normal development work. Sure, there are some serious bugs left, but you
have to try pretty hard to actually hit those. There are some ways of stressing
the system that make Haiku's kernel crash, but my personal experience is that I
can work just fine for at least a day. For using some of the new Haiku
features, like writing applications that use the layout
management, it's just way more convenient to develop and test in Haiku at
this point. Due to the much better caching, the system is usually way faster
too.
Best regards,
-Stephan
Other related posts:
