Re: Announcing early any changes on the try server and the exact build envs

2014-06-04 Thread Daniel Holbert
On 06/03/2014 07:32 AM, Gabor Krizsanits wrote: 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. FWIW, you can work around that with ac_add_options

Re: Announcing early any changes on the try server and the exact build envs

2014-06-04 Thread Daniel Holbert
On 06/03/2014 04:25 PM, Mike Hommey wrote: 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. I think that might be putting it a bit too strongly. Warnings-as-errors absolutely *is* meant to be used with

Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Gabor Krizsanits
From time to time, no matter what platform I use, the build configuration on the try server changes and from that point on it's just a matter of time that my build gets broken. When you're about to work on some urgent fixes, it can be very frustrating to try and fix the build instead... I

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Ben Hearsum
On 14-06-03 06:39 AM, Gabor Krizsanits wrote: From time to time, no matter what platform I use, the build configuration on the try server changes and from that point on it's just a matter of time that my build gets broken. When you're about to work on some urgent fixes, it can be very

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Gabor Krizsanits
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

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Ben Hearsum
On 14-06-03 10:32 AM, 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

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Gregory Szorc
On 6/3/14, 6:42 AM, Ben Hearsum wrote: On 14-06-03 06:39 AM, Gabor Krizsanits wrote: From time to time, no matter what platform I use, the build configuration on the try server changes and from that point on it's just a matter of time that my build gets broken. When you're about to work on

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Mike Hommey
On Tue, Jun 03, 2014 at 09:11:26AM -0700, Gregory Szorc wrote: On 6/3/14, 6:42 AM, Ben Hearsum wrote: On 14-06-03 06:39 AM, Gabor Krizsanits wrote: From time to time, no matter what platform I use, the build configuration on the try server changes and from that point on it's just a matter of

Re: Announcing early any changes on the try server and the exact build envs

2014-06-03 Thread Mike Hommey
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?