Re: Path forward to C++11.

2014-08-29 Thread Dominic Hamon
.6.x >>> >>> So we already do not support gcc 4.7 for C++11. >>> >>> It's important here to make the distinction that this is for development, >>> ideally those are running from RPMs are agnostic to the gcc version used. >>> But, I suppose the

Re: Path forward to C++11.

2014-08-28 Thread Dominic Hamon
gt; >> It's important here to make the distinction that this is for development, >> ideally those are running from RPMs are agnostic to the gcc version used. >> But, I suppose the c++11 shared library will not present on the machine. >> >> On Wed, Feb 26, 201

Re: Path forward to C++11.

2014-02-26 Thread Dominic Hamon
But, I suppose the c++11 shared library will not present on the machine. > > On Wed, Feb 26, 2014 at 12:08 PM, Dominic Hamon >wrote: > > > Forwarding from the right account to avoid Spam filters ... > > > > ------ Forwarded message -- > > From: Domi

Re: Path forward to C++11.

2014-02-26 Thread Benjamin Mahler
e -- > From: Dominic Hamon > Date: Wed, Feb 26, 2014 at 11:46 AM > Subject: Re: Path forward to C++11. > To: dev@mesos.apache.org > > > What do you mean by 'C++11 support' in the compiler? g++4.7 supports some > features, not all. > > I think we need to

Fwd: Path forward to C++11.

2014-02-26 Thread Dominic Hamon
Forwarding from the right account to avoid Spam filters ... -- Forwarded message -- From: Dominic Hamon Date: Wed, Feb 26, 2014 at 11:46 AM Subject: Re: Path forward to C++11. To: dev@mesos.apache.org What do you mean by 'C++11 support' in the compiler? g++4.7 sup

Re: Path forward to C++11.

2014-02-26 Thread Dominic Hamon
t;> prior to 'configure', and it failed compilation pretty quickly. > >> It may make sense to track integration issues and versions...somewhere. > >> > >> So when --with-cpp11 is enabled, it can hard check on version >= > >> fixed_version. > >> > >

Re: Path forward to C++11.

2014-02-26 Thread Benjamin Mahler
quickly. >> It may make sense to track integration issues and versions...somewhere. >> >> So when --with-cpp11 is enabled, it can hard check on version >= >> fixed_version. >> >> Cheers, >> Tim >> >> - Original Message - >> >

[jira] [Assigned] (MESOS-323) Get mesos compiling with clang to open up path forward to c++11

2014-01-14 Thread Benjamin Hindman (JIRA)
[ https://issues.apache.org/jira/browse/MESOS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman reassigned MESOS-323: -- Assignee: Benjamin Hindman > Get mesos compiling with clang to open up path forward

[jira] [Resolved] (MESOS-323) Get mesos compiling with clang to open up path forward to c++11

2014-01-14 Thread Benjamin Hindman (JIRA)
up path forward to c++11 > --- > > Key: MESOS-323 > URL: https://issues.apache.org/jira/browse/MESOS-323 > Project: Mesos > Issue Type: Task >R

Re: Path forward to C++11.

2013-10-28 Thread Benjamin Mahler
ere. > > So when --with-cpp11 is enabled, it can hard check on version >= > fixed_version. > > Cheers, > Tim > > - Original Message - > > From: "Benjamin Mahler" > > To: dev@mesos.apache.org > > Sent: Wednesday, October 23, 2013 4:46:49 PM >

Re: Path forward to C++11.

2013-10-24 Thread Tim St Clair
. It may make sense to track integration issues and versions...somewhere. So when --with-cpp11 is enabled, it can hard check on version >= fixed_version. Cheers, Tim - Original Message - > From: "Benjamin Mahler" > To: dev@mesos.apache.org > Sent: Wednesday, October

Re: Path forward to C++11.

2013-10-23 Thread Vinod Kone
+1 @vinodkone On Wed, Oct 23, 2013 at 2:52 PM, Jie Yu wrote: > +1 > > LGTM > > > On Wed, Oct 23, 2013 at 2:46 PM, Benjamin Mahler > wrote: > > > As discussed in MESOS-750 < > https://issues.apache.org/jira/browse/MESOS-750 > > >, > > we would like to move to C++11. > > > > The proposed plan i

Re: Path forward to C++11.

2013-10-23 Thread Jie Yu
+1 LGTM On Wed, Oct 23, 2013 at 2:46 PM, Benjamin Mahler wrote: > As discussed in MESOS-750 >, > we would like to move to C++11. > > The proposed plan is to do this in phases to allow everyone time to adjust > to this change: > > > Phase 1: Sen

Path forward to C++11.

2013-10-23 Thread Benjamin Mahler
As discussed in MESOS-750 , we would like to move to C++11. The proposed plan is to do this in phases to allow everyone time to adjust to this change: Phase 1: Send an email to the dev@ list soliciting objections / feedback. We're currently here.

[jira] [Updated] (MESOS-323) Get mesos compiling with clang to open up path forward to c++11

2013-09-20 Thread Benjamin Mahler (JIRA)
ard to c++11 > --- > > Key: MESOS-323 > URL: https://issues.apache.org/jira/browse/MESOS-323 > Project: Mesos > Issue Type: Task >Reporter: Benjamin Mahl

[jira] [Updated] (MESOS-323) Get mesos compiling with clang to open up path forward to c++11

2013-09-20 Thread Benjamin Mahler (JIRA)
[ https://issues.apache.org/jira/browse/MESOS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-323: -- Priority: Minor (was: Major) > Get mesos compiling with clang to open up path forward t

[jira] [Commented] (MESOS-323) Get mesos compiling with clang to open up path forward to c++11

2013-09-20 Thread Benjamin Mahler (JIRA)
ttps://reviews.apache.org/r/13473/ https://reviews.apache.org/r/13840/ https://reviews.apache.org/r/13879/ https://reviews.apache.org/r/13598/ > Get mesos compiling with clang to open up path forward t