[haiku-development] Re: GCC 4.4.0
- From: Joseph Prostko <joe.prostko+haiku@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 22 Apr 2009 11:00:54 -0400
On Sat, Mar 28, 2009 at 6:27 PM, Joseph Prostko
<joe.prostko+haiku@xxxxxxxxx> wrote:
> I know we just got GCC 4.3.3 lately, but seeing as GCC 4.4.0 is the
> current release series now, are there any plans to incorporate this
> into Haiku?
Well, seeing as I knew that GCC 4.4.0's release was due soon, I
started working on porting it this weekend. The official release
happened what is now yesterday, and I applied all of my changes to it.
Keep in mind that I pretty much just applied Michael Lotz's changes
to GCC 4.4.0, so I thank him for that.
The build I have is without Graphite at the moment, but that is mostly
because I wanted to take a "one thing at a time" approach.
Right now I have only built it as a cross-compiler, so it still needs
to be built natively at some point. Thanks to an insight by Rene
Gollent, I produced a patch to build Haiku under 4.4.0, due to some
changes it has (stricter checks, basically).
Unfortunately, I wasn't able to boot into Haiku (it got all confused
when looking at my hard drive partitions according to the syslog), but
I am rebuilding the cross tools with GCC 4.4.0 final right now,
instead of the RC I was using previously. I am also not configuring
with -without-werror this time around, so likely more problems in
Haiku code outside of the kernel will creep up.
While I don't think the problem I had with booting will magically go
away (there's likely some things wrong with the "port"), it's at least
a good start to know that Haiku builds. It also goes to show that not
much work will be needed to make sure it is ported correctly.
Well, I thought I'd announce that anyways. I'm sure nobody is in any
hurry to push GCC 4.4.0 to Haiku at the moment, but I wanted you all
to know it's at least possible to get as far as compiling Haiku with
most only Michael's 4.3.3 handywork.
By the way, I did notice that the license in 4.4.0 changed to include
a run-time license that affects projects such as Objective Caml. I
don't think this impacts us in any way though, but thought I'd mention
it.
- joe
Other related posts:
