|
- Haiku by default uses the relatively ancient GCC 2.95.3 (released in March 2001). This is done to maintain ABI compatibility for the original x86 BeOS applications.
- GCC4 options are also available in Haiku. Actually, there seems to be 2 options, known as GCC2/4 hybrid and GCC4/2 hybrid. I don't yet know the details of what exactly is built with GCC2/4 versus GCC4/2. The hybrid builds let you run binaries compiled and linked with both GCC2 and GCC4.
- An e-mail thread from the Haiku development list discussing the hybrid builds can be found here: http://www.freelists.org/post/haiku-development/How-to-build-Haiku-R1Alpha-1,7
- Here is how I setup my first GCC2/4 and GCC4/2 hybrid builds:
- type: cd ~/
- type: svn checkout http://svn.haiku-os.org/haiku/haiku/trunk haiku/trunk
- type: cd ~/haiku/trunk
- type: mkdir generated.gcc2
- type: mkdir generated.gcc4
- type: cd generated.gcc4
- type: ../configure --alternative-gcc-output-dir ../generated.gcc2 --cross-tools-prefix /boot/develop/abi/x86/gcc4/tools/current/bin/
- type: cd ../generated.gcc2
- type: ../configure --alternative-gcc-output-dir ../generated.gcc4
- At this point in time, things are setup for either a GCC2/4 or GCC4/2 hybrid build. If you build in generated.gcc2 you get a GCC2/4 build:
- type: cd ~/haiku/trunk/generated.gcc2
- type: jam -j3 -q haiku-cd
- Or, to get a GCC4/2 hybrid build:
- type: cd ~/haiku/trunk/generated.gcc4
- type: jam -j3 -q haiku-cd
- If the build was successful, I'd expect to find a generated/haiku-cd.iso file that I could then boot and install overtop of my existing Haiku partition; see the last step in Your First Haiku Build.
|
|