On Tue, Jan 3, 2017 at 7:05 AM, Ben Kelly wrote:
> FWIW, it seems ./mach bootstrap does not install gcc 4.9 on ubuntu 14.04.
It looks like it's not packaged for 14.04; so we'd have to add a ppa
to do this prior to 16.04.
-r
___
dev-platform mailing l
FWIW, it seems ./mach bootstrap does not install gcc 4.9 on ubuntu 14.04.
On Fri, Dec 23, 2016 at 11:08 AM, Nathan Froyd wrote:
> Bug 1322792 has landed on inbound, which changes configure to require
> GCC 4.9 to build; our automation switched over to GCC 4.9 for our
> Linux builds earlier this
On 2016/12/24 1:54, Nathan Froyd wrote:
On Fri, Dec 23, 2016 at 11:37 AM, Mike Hoye wrote:
On 2016-12-23 11:08 AM, Nathan Froyd wrote:
Bug 1322792 has landed on inbound, which changes configure to require
GCC 4.9 to build; our automation switched over to GCC 4.9 for our
Linux builds earlier th
On 2016-12-23 6:39 PM, gsquel...@mozilla.com wrote:
>> paves the way for being able to compile in C++14
> So, can we start using the good stuff right now, or should we wait for a
> proper "go" signal?
Bug 1325632 needs to be fixed first. Currently we still build in C++11
mode.
_
On Fri, Dec 23, 2016 at 6:39 PM, wrote:
> On Saturday, December 24, 2016 at 3:08:21 AM UTC+11, Nathan Froyd wrote:
>> paves the way for being able to compile in C++14
> So, can we start using the good stuff right now, or should we wait for a
> proper "go" signal?
We'll need to wait for bug 1325
On Saturday, December 24, 2016 at 3:08:21 AM UTC+11, Nathan Froyd wrote:
> Bug 1322792 has landed on inbound, which changes configure to require
> GCC 4.9 to build; our automation switched over to GCC 4.9 for our
> Linux builds earlier this week. (Android builds have been using GCC
> 4.9 for some
On 2016-12-23 11:08 AM, Nathan Froyd wrote:
> This change paves the way for being able to compile in C++14 mode for
> all of our Tier-1 platforms, which in turn unlocks using some C++14
> features in our codebase:
>
> * binary literals
> * digit separators
> * generic lambdas
> * initialized lambd
On Fri, Dec 23, 2016 at 11:37 AM, Mike Hoye wrote:
> On 2016-12-23 11:08 AM, Nathan Froyd wrote:
>> Bug 1322792 has landed on inbound, which changes configure to require
>> GCC 4.9 to build; our automation switched over to GCC 4.9 for our
>> Linux builds earlier this week. (Android builds have be
On 2016-12-23 11:08 AM, Nathan Froyd wrote:
Bug 1322792 has landed on inbound, which changes configure to require
GCC 4.9 to build; our automation switched over to GCC 4.9 for our
Linux builds earlier this week. (Android builds have been using GCC
4.9 for some time.)
I happened to be poking
Bug 1322792 has landed on inbound, which changes configure to require
GCC 4.9 to build; our automation switched over to GCC 4.9 for our
Linux builds earlier this week. (Android builds have been using GCC
4.9 for some time.)
This change paves the way for being able to compile in C++14 mode for
all
10 matches
Mail list logo
