while the binaries themselves should run, there are several differences between the architectures, first in terms of system paths (libraries in /boot/system/lib/x86 instead of /boot/system/lib, for example), and because of this, we need to build some packages twice.
As a result, the packages for gcc2-hybrid and gcc5-hybrid are not in sync, which means you don't always have the same version of libraries, etc.
So, we must have two independant set of packages.
This is indeed rather confusing, so what I would suggest (and the current plan for beta1) is:
- Deprecate the gcc5hybrid
- Keep gcc2hybrid as the only variant which supports BeOS apps, with maximal compatibility
- Keep x86_64 as the variant for people who don't care about BeOS compatible apps
Eventually, we could build an x86_64 system with some gcc2-32-bit wrapper so it can still run BeOS apps. But there is some more work needed before we get to that, so it is likely that this will happen only in R2, or we may just give up on it if gcc2 support becomes too irrelevant.