[haiku-commits] Re: haiku: hrev44719 - build/jam
- From: Joseph Prostko <joe.prostko@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sat, 27 Oct 2012 08:05:48 -0400
On Sat, Oct 27, 2012 at 7:48 AM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> Siarzhuk Zharski wrote:
>> Do you mean the following?
>> a) add headers/gnu into GCC's built-in headers list;
>> b) wait the next planned recompilation of buildtools;
>> c) roll back hrev44719;
>
> Well, start with c). That had been the status quo for years. It just requires
> any ported project using the xattr support to configure with the gnu
> directory added explicitly. It can be removed again once the GCCs have been
> updated, but doesn't do any harm afterwards either. There's no recompilation
> planned for either GCC. GCC 2 only needs to be rebuilt when something
> changes. For GCC 4 we can assume that it gets updated to a newer version
> eventually.
Actually, for fun I was playing with an update to GCC 4.7.2 locally.
Unfortunately (fortunately?) it is much more strict about things due
to its C++11 compliance, and the Haiku build bombs out early in
VMAnonymousCache.cpp due to issues involving narrowing conversion.
Anyway, my point of bringing this up at all is that while working on
this, I noticed we have a lot of residual references to
/boot/beos/system/lib in our buildtools directory (instead of
/boot/system/lib). I planned on fixing this at some point, but having
to address the whole gnu search path means that both should probably
get fixed at the same time.
>> IMO we have too much buildtools updates last days to force yet another
>> rebuild due cosmetic issue. From the other side we will living with
>> Alpha4 at least for the next year so it is better to polish this issue
>> too.
>
> I don't think the GCC update is urgent. Though it certainly doesn't harm to
> do it before it is forgotten. Or add least add a TODO somewhere (e.g. in the
> Wiki).
I don't think it harms to update either (other than taking up more
space on haiku-files.org), and I'd have no problem doing another
rebuild of both for R1A4 tomorrow after I'm sure all of the server
updates are completed. Siarzhuk, feel free to patch up the GCC files
as needed for the header path if you want, or if you don't, I'll get
around to doing that as well while I'm making my own changes.
- joe
Other related posts:
