Update on MESOS-750: 0.17.0 is being released with the --with-cxx11 capability at configure time.
I chatted with some of the committers and we'd like to move forward with the final two phases of MESOS-750 as follows: 0.18.0: --with-cxx11 will become the _default_. --without-cxx11 will be available for those who wish to use older compilers. 0.19.0: c++11 required; Mesos will not build with a compiler that does not have c++11 support. If there are any objections please speak now. If not, I'll update the ticket to reflect the current path towards C++11. On Mon, Oct 28, 2013 at 8:09 PM, Benjamin Mahler <[email protected]>wrote: > Thanks for the heads up, we're likely to upgrade to 3.3.6, but I've yet to > confirm that it builds with c++11. > > > On Thu, Oct 24, 2013 at 8:10 AM, Tim St Clair <[email protected]> wrote: > >> +1 to the approach. >> >> FWIW made a quick update to the zookeeper.spec ( >> http://koji.fedoraproject.org/koji/buildinfo?buildID=465529) and updated: >> >> export CC='gcc -std=c11' >> export CXX='g++ -std=c++11' >> >> 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. >> >> Cheers, >> Tim >> >> ----- Original Message ----- >> > From: "Benjamin Mahler" <[email protected]> >> > To: [email protected] >> > Sent: Wednesday, October 23, 2013 4:46:49 PM >> > Subject: Path forward to C++11. >> > >> > As discussed in MESOS-750 < >> https://issues.apache.org/jira/browse/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. :) >> > >> > Phase 2: Add an option --with-cpp11 that defaults to false. >> > >> > Phase 3: At this point, developers can and should begin using >> --with-cpp11. >> > In this phase, we'll need to make sure the project and dependencies can >> > compile with c++11. >> > >> > Phase 4: Default to --with-cpp11 but still leave the option in order to >> > allow folks to turn this off if needed. At this point, we still cannot >> rely >> > on C++11. >> > >> > Phase 5: Remove --with-cpp11 leaving no ability to turn it off. From >> this >> > point forward, we can begin to use C++11 features unconditionally. >> > >> > >> > Please reply to this thread with any objections, comments, or advice! To >> > get a better sense of how others feel about this (I currently only know >> > that some of the other core contributors are on board), please feel >> free to >> > reply with something as simple as a +1 as well. >> > >> > Thanks! >> > Ben >> > >> >> -- >> Cheers, >> Tim >> > >
