On Tue, Jun 03, 2014 at 07:32:57AM -0700, Gabor Krizsanits wrote: > > > > It's pretty rare that things such OS, Compiler, SDK change on our build > > systems. We do tend to make noise about them when that happens, too. Do > > you have specific examples to point at? > > Where can I follow these changes? One specific example is bug 1002729 and the > like... > Currently m-c does not build with gcc 4.6 on ubuntu because something > similar. After > updating to 4.8 I got some warning in webrtc code, so I had to turn off > warning-as-errors. > > In the past we changed required windows SDK unannounced too... That being > said I can > totally imagine that I don't follow the right channels where these kind of > changes > are announced. For example, do we have a way to tell the exact configurations > on the > try server? Like exact gcc version / linux version...
The last GCC version change was to 4.7, a year ago[1], and it was announced[2]. Since then, we've only changed how the GCC we use is installed, and bumped from 4.7.2 to 4.7.3. Now, considering that our automation uses GCC 4.7 to build, yes, there can be changes that break building with other compilers, be they newer versions, older versions, or other compilers. That happens regularly. Those are bugs, should be reported as such, and should be fixed, unless we decide that we stop supporting GCC < 4.7 (but we still need to support GCC 4.4 for b2g...). As for warning-as-errors, it's not meant to be used for local builds, because different compilers don't come with the same set of warnings. So when compiling with a compiler that doesn't match what's used on automation, yes, you risk hitting new warnings, and failing to build as a consequence. Mike 1. https://hg.mozilla.org/mozilla-central/rev/8d46dcc704d7 2. https://groups.google.com/d/msg/mozilla.dev.platform/AUaI3Uk80gc/evXDzFeAJscJ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
