[haiku-development] Re: Updates relating to build-o-matic, haiku-files.org

  • From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 17 May 2011 19:59:03 +0100

Le 17/05/2011 19:26, Urias McCullough a écrit :
On Tue, May 17, 2011 at 10:46 AM, pulkomandy
<pulkomandy@xxxxxxxxxxxxxxxxx>  wrote:
Since Alpha3 looks like it is going to be another gcc2hybrid - does it
even make sense to distribute gcc4 with it any more? I thought it was
generally "useless" to use gcc4 on a gcc2hybrid any longer.
It is discouraged, but still useful. People may want to build Web+, for
example. It's clearly stated in the release notes that it is
"experimental" and the API will not be kept accross releases for gcc4.
Perhaps we should introduce more API breakage to make that clearer ;)
I keep reading Ingo's satements that compilation of gcc4 software on a
gcc2hybrid is discouraged...so how can webpositive be compiled on
gcc2hybrid without concerns?
Ah yes, the symbolic linking stuff.
For some time we've had compatibility between C apps compiled for gcc2/4. This means it is possible to make some bridge between the two compilers using C (not C++, because of the different mangling). However, this was never supported, and is now known to be broken because of the different symbol resolution.

It is still safe to use gcc4 in a gcc2hybrid and build apps with that, the result will be working, the only constraint is that any later release of Haiku will likely not run it anymore (while an app compiled with gcc2 will work at least until R1, maybe even R2). This allows us to update the gcc4 API smoothly, while people still use the stable gcc2 one.


Other related posts: