I think the gonk parts always use the provided AOSP toolchain for building, while gecko uses the compiler provided by the system when building for the host.
In any case I had a keon (ICS) build fail to compile libmar with gcc 4.6 due to the new requirement. Using gcc 4.8 on the system instead worked fine for building from scratch, including an OTA package - which IIRC builds some AOSP tooling for the host. Dolphin is kitkat so not affected. Not sure about the Nexus. *Andreas Pehrson *--- Software Engineer (+47) 959 60 374 | pehr...@telenordigital.com | www.telenordigital.com On Wed, Mar 25, 2015 at 3:39 PM, Mike Hommey <m...@glandium.org> wrote: > On Wed, Mar 11, 2015 at 02:56:27PM -0700, Juan Gómez wrote: > > AFAIK, in B2G we are tied to the same host compiler version that our > > Android base platform needs. This is gcc-4.6 for ICS and JB devices > > (not really sure if KK/LL works with newer ones, but I'll bet they > > do). > > I overlooked this when I (re)landed bug 1142352, and the host compiler > version we now require on central (well, inbound as of writing) is 4.7. > This didn't blow up B2G device images on treeherder so I guess we are > ok, OTOH, I don't know if Nexus 4 and Dolphin images are ICS/JB or KK/L. > > We /could/ repatch to make 4.6 the minimum for host compiler, but not > having the same minimum version between host and target is dangerous > because some of the host code is using MFBT and may end up requiring 4.7 > through MFBT anyways. > > Mike > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
