[haiku-development] Re: [haiku] Re: Future releases? Recommend nightlies? gcc2?
- From: kallisti5 <kallisti5@xxxxxxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Wed, 30 Nov 2016 20:08:44 -0600
On November 30, 2016, at 4:03 PM, kallisti5 <kallisti5@xxxxxxxxxxx>
wrote:
Now on to the bigger elephant...
I personally still *really* want to see R1 to be x86 gcc4h (cough
gcc5h).
I think we missed the gcc2h boat years ago.
gcc2h in 2006 made sense.
gcc2h in 2016 makes 0 sense.
The list of software that even compiles on gcc2 is shrinking
rapidly...
why are we doing this to ourselves?
gcc4h (gcc5h now) means you can run BeOS apps, and have a native
modern
compiler. The downside is users
won't be able to run BeOS replicants, drivers, or screensavers on R1.
At this point in time, I can't think of a single "must have 1999 BeOS
replicant" (that isn't open sourced).
There may be folks out there however i'm not thinking of.
So once again, why are we doing this to ourselves?
On 2016-11-30 19:13, Dennis Catt wrote:
Well I think that Haiku A4 should remain available until B1 is made
available. We definitely need to do comparison testing to ensure B1
will perform as well as A4 from a stability, performance and
reliability perspective.
What's the deal with replicants, drivers and screensavers not working
with newer GCC versions? Just curious.
There is a binary incompatibility between gcc2 and gcc5 binaries (ABI)
We have the hybrid builds that include duplicate gcc2 copies of system
libraries on the gcc5 system, however (running) tracker, (running)
kernel,
and (running) app_server are only gcc5 on gcc5 systems.
Drivers,screensavers,replicants aren't independent applications, they
load
almost like plugins within a process.
gcc2 drivers won't be compatible with the gcc5 kernel
gcc2 screensavers won't be compatible with the gcc5 app_server
gcc2 replications won't be compatible with the gcc5 tracker.
You can only have one running kernel,app_server,tracker ;-)
-- Alex
Other related posts:
