On 01/03/11 07:00, Jim Huang wrote:
I think thats fine. however, how do we ensure that we have patches
that always apply to both release/snapshots? do we maintain branches for gcc-patches.git in case you need two versions of patch X if the linaro gcc codebase diverged?
I might need help from toolchain WG.
I aim to have Android support in Linaro GCC soon, but I lack the ability to test it. In fact, I have wanted to have Android support in both February's and March's release, but it isn't going to happen now.
I did build a Linaro GCC with the Android patches installed, and it did appear to build a lot of the Android tree, but the Android build is broken. There are problems with -Werror, but even when you work around those, it still won't build. :(
When somebody gives me a properly patched Android tree, that will build out-of-the-box with GCC 4.6, then I will be unblocked, and Linaro GCC will have Android support shortly afterwards. :)
Andrew