[haiku-development] Re: Coordinating porting efforts
- From: "Fredrik Holmqvist" <fredrik.holmqvist@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 17 Feb 2008 13:21:59 +0100
2008/2/17, Simon Taylor <simontaylor1@xxxxxxxxxxxx>:
> Fredrik Holmqvist wrote:
> > One new problem with gcc4 and ports is that gcc reports the architecture
> > as haiku instead of beos.
> > It's also a bit confusing as gcc2 is still beos, so when doing gcc4
> > builds configure will almost always fallback to the default arch instead
> > of the beos alternative.
>
> This does sound confusing, I'd vote for switching to reporting the same
> architecture for both compilers. I'd probably favour -haiku and
> documenting that this has changed (IIRC, we're not actually concerned
> with exact source compatibility with BeOS anyway (header layout etc)?)
>
>
From what I've come to understand this is actually the case for the
compilers that are built when building Haiku. Correct me if I'm wrong.
--
Fredrik Holmqvist
Chaordic: things that thrive on the edge of chaos with just enough order to
give them pattern, but not so much to slow their adaptation and learning.
Other related posts:
