[haiku-development] R1/Alpha1: Prop # 4: Release as the GCC 2/4 hybrid
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 22 May 2009 21:30:08 +0000
First and foremost, this is not an indication that R1/Alpha1 is ready.
The purpose of this thread is to revisit the decision to release
R1/Alpha1 as a gcc2-hybrid.
http://dev.haiku-os.org/wiki/R1/Alpha1Proposals#Prop4:ReleaseastheGCC24hybrid
This will hopefully allow us to:
* identify the issues that prevent a hybrid image from functioning as expected
* estimate the complexity of resolving those issues
* determine this is indeed a wanted and needed functionality for R1/Alpha1
Here are some current issues with hybrids
(disclaimer, i could very well be incorrect about these details)
1- Translator presentation
Eg, on on gcc4-hybrid, WonderBrush (a gcc2 only app) will appear to
fail, due to being presented gcc4-translators.
2- Cannot compile programs for the alternate libs
Eg, on a gcc2-hybrid system, an end user cannot create gcc4 binaries
or vice versa.
3- Haiku itself cannot build the alternate gcc of itself.
Eg, a gcc2 system cannot create a gcc4 build of Haiku or vice versa.
4- Aside from gnash, what is the list of software that is exclusive to gcc4?
Note, WebKit is also gcc4-exclusive, but as of today, it isn't ready
for distribution.
Any thoughts on having haiku-files.org provide gcc2hybrid and/or
gcc4hybrid images?
--mmadia
Other related posts:
