3 ms·
I remember porting gcc 3 and GDB to BeOS. Reading this article, it doesn't look like the 32 bit version ever progressed past that :)
by DannyBee 9y ago
I remember porting gcc 3 and GDB to BeOS.
Reading this article, it doesn't look like the 32 bit version ever progressed past that :)
- badsectoracula 9y agoAFAIK the problem lies with GCC breaking the ABI. Haiku tries to solve the issue by building the userspace APIs with multiple GCC versions to preserve the ABI for older apps. I do not think this is a good idea in long term though since you need to keep older GCC versions around to provide backwards compatibility and make sure your C++ code compiles with all GCC versions from 2 to whatever is the latest one. A better solution would be for GCC to provide means for working with binaries and libraries produced with older versions of the C++ compiler, ideally including 2. Perhaps a more realistic solution would be to create "proxy" libraries for the previous GCC versions that all they do is to redirect the calls to the latest version.
- rvense 9y agoOpenBeOS started just after Be folded. Binary compatibility was a priority, and remained so for a long time. I think especially still having an office suite (Gobe Production) was important, but it is my impression that this concern has faded.