Yeah, upgarding to gcc 4.8 was a bit tough but it established the basis for less compllcated upgardes in the future. I could compile all FFOS flavors (ICS, JB, KK and LL) using gcc-4.9 base toolchain without any remarcable complication. My plan was to upgrade to gcc 4.9 [1] last year, but we had to stop it becuase we needed the partner confirmation to move forward. Now that we don't need that confirmation, we could resume the work and land gcc-4.9 support.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1087161 On Mon, Jan 25, 2016 at 6:40 PM, Fabrice Desré <fabr...@mozilla.com> wrote: > On 01/25/2016 09:30 AM, Ehsan Akhgari wrote: > > > For example, for a long time b2g partners held back our minimum > > supported gcc. Now that there are no such partner requirements, perhaps > > we can consider bumping up the minimum to gcc 4.8? (bug 1175546) > > We moved to 4.8 on b2g a year ago: see > https://bugzilla.mozilla.org/show_bug.cgi?id=1056337 > Who's behind? :P > > > Another example, last year because of 2.5 release pressure where people > > were planning on using service workers in gaia app, we had to add a huge > > hack for "supporting" app:// URIs for service worker interception. The > > last time that this code bit me was earlier this morning. It would be > > nice if I can remove this broken code now instead of worrying about how > > to keep supporting it going forward (this makes fixing bug 1222008 more > > complicated than it needs to be.) > > I have no objections to remove this particular support. > > -- > Fabrice Desré > Connected Devices > Mozilla Corporation > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > -- ___________________ Juan Gómez Mosquera Platform Engineer Mozilla Corporation _AtilA_ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
