bootstrap is complex and error prone

[kallisti5]

Our current bootstrap process is extremely complex and error prone. We really need to reduce some of the complexity of the initial bootstrap. Port progress is at a standstill as you have to have an entire bootstrap completed before doing any port work on bootloader, kernel, etc.

Ideas:

• Create a new single repo with the most basic tools forked. We tune the build scripts to be easily executable within the initial bootstrap environment. We generate one haiku_bootstrap_env hpkg that provides a basic environment. (coreutils,awk,bison,curl,mawk,flex,m4,make,sed)
• Fork busybox and make a simple busybox fork to provide all of the core utils + sed,awk,wget,etc. I have a busybox binary generated on Haiku after some tweaking... their build system is really rough however and can be flaky when automated.
• Introduce a new @basic-raw target which doesn't require a bootstrap. Just include bootloader, filesystem drivers, kernel.

[kallisti5]

arm bootstrap after two days of work.