Re: Changing Mesos Minimum Compiler Version

[Joris Van Remoortere]

Re: GCC 5.x, specifically section [2]
https://gcc.gnu.org/gcc-5/changes.html#offload

Although these changes are great, I'm not sure we currently need them for
Mesos itself.
I agree with you that they could make lots of frameworks rock, and I don't
think the gcc version for mesos prevents that:

   - We use protobufs to communicate between services which allows:
   - Executors can be compiled using a totally different compiler from
   Apache Mesos
   - Frameworks can be compiled using a totally different compiler from
   Apache Mesos
   - This means you can have a super optimized custom executor that takes
   advantage of all the benefits of GCC 5.X running on a Mesos built on GCC
   4.8 or Clang 3.5!

Hopefully this clarifies why this is not actually crucial, and why you
won't be missing out on any benefits!

Joris

On Tue, Apr 21, 2015 at 10:27 AM, Cody Maloney  wrote:

> The main holdup at the moment is simply cycles I have to convert our
> internal infrastructure for packaging mesos on all the distributions to use
> newer compilers on all those distributions. I want the infrastructure for
> supporting the change in place before we make it. I have about 1/3 of the
> work done (Can build on all distros except Debain Wheezy). I've gotta add
> the packaging steps (Shouldn't be too bad), and some glue code still
> though.
>
> On Tue, Apr 21, 2015 at 3:07 AM, Alex Rukletsov 
> wrote:
>
> > Folks, let's summarize and move on here.
> >
> > Proposal out on April 9, 2015. Current status (as of April 21, 2015):
> >
> >
> > +1 (Binding)
> > --
> > Vinod Kone
> > Timothy Chen
> > Yan Xu
> > Brenden Matthews
> >
> > +1 (Non-binding)
> > --
> > Cody Maloney
> > Joris Van Remoortere
> > Jeff Schroeder
> > Jörg Schad
> > Elizabeth Lingg
> > Alexander Rojas
> > Alex Rukletsov
> > Michael Park
> > Haosdent Huang
> > Bernd Mathiske
> >
> > 0 (Non-binding)
> > --
> > Nikolaos Ballas
> >
> > There were no -1 votes.
> >
> > Cody, let's convert MESOS-2604 to an epic and bump the version in 0.23.
> >
> > Thanks,
> > Alex
> >
> >
> > On Mon, Apr 13, 2015 at 12:46 PM, Bernd Mathiske 
> > wrote:
> >
> >> +1
> >>
> >> > On Apr 10, 2015, at 6:02 PM, Michael Park  wrote:
> >> >
> >> > +1
> >> >
> >> > On 9 April 2015 at 17:33, Alexander Gallego 
> >> wrote:
> >> >
> >> >> This is amazing for native devs/frameworks.
> >> >>
> >> >> Sent from my iPhone
> >> >>
> >> >>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere <
> jo...@mesosphere.io
> >> >
> >> >> wrote:
> >> >>>
> >> >>> +1
> >> >>>
> >>  On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney 
> >> >> wrote:
> >>  As discussed in the last community meeting, we'd like to bump the
> >> >> minimum required compiler version from GCC 4.4 to GCC 4.8.
> >> 
> >>  The overall goals are to make Mesos development safer, faster, and
> >> >> reduce the maintenance burden. Currently a lot of stout has different
> >> >> codepaths for Pre-C++11 and Post-C++11compilers.
> >> 
> >>  Progress will be tracked in the JIRA: MESOS-2604
> >> 
> >>  The resulting supported compiler versions will be:
> >>  GCC 4.8, GCC 4.9
> >>  Clang 3.5, Clang 3.6
> >> 
> >>  For reference
> >>  Compilers by Distribution Version: http://goo.gl/p1t1ls
> >> 
> >>  C++11 features supported by each compiler:
> >>  https://gcc.gnu.org/projects/cxx0x.html
> >>  http://clang.llvm.org/cxx_status.html
> >> >>>
> >> >>
> >>
> >>
> >
>

Re: Changing Mesos Minimum Compiler Version

[Cody Maloney]

The main holdup at the moment is simply cycles I have to convert our
internal infrastructure for packaging mesos on all the distributions to use
newer compilers on all those distributions. I want the infrastructure for
supporting the change in place before we make it. I have about 1/3 of the
work done (Can build on all distros except Debain Wheezy). I've gotta add
the packaging steps (Shouldn't be too bad), and some glue code still though.

On Tue, Apr 21, 2015 at 3:07 AM, Alex Rukletsov  wrote:

> Folks, let's summarize and move on here.
>
> Proposal out on April 9, 2015. Current status (as of April 21, 2015):
>
>
> +1 (Binding)
> --
> Vinod Kone
> Timothy Chen
> Yan Xu
> Brenden Matthews
>
> +1 (Non-binding)
> --
> Cody Maloney
> Joris Van Remoortere
> Jeff Schroeder
> Jörg Schad
> Elizabeth Lingg
> Alexander Rojas
> Alex Rukletsov
> Michael Park
> Haosdent Huang
> Bernd Mathiske
>
> 0 (Non-binding)
> --
> Nikolaos Ballas
>
> There were no -1 votes.
>
> Cody, let's convert MESOS-2604 to an epic and bump the version in 0.23.
>
> Thanks,
> Alex
>
>
> On Mon, Apr 13, 2015 at 12:46 PM, Bernd Mathiske 
> wrote:
>
>> +1
>>
>> > On Apr 10, 2015, at 6:02 PM, Michael Park  wrote:
>> >
>> > +1
>> >
>> > On 9 April 2015 at 17:33, Alexander Gallego 
>> wrote:
>> >
>> >> This is amazing for native devs/frameworks.
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere > >
>> >> wrote:
>> >>>
>> >>> +1
>> >>>
>>  On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney 
>> >> wrote:
>>  As discussed in the last community meeting, we'd like to bump the
>> >> minimum required compiler version from GCC 4.4 to GCC 4.8.
>> 
>>  The overall goals are to make Mesos development safer, faster, and
>> >> reduce the maintenance burden. Currently a lot of stout has different
>> >> codepaths for Pre-C++11 and Post-C++11compilers.
>> 
>>  Progress will be tracked in the JIRA: MESOS-2604
>> 
>>  The resulting supported compiler versions will be:
>>  GCC 4.8, GCC 4.9
>>  Clang 3.5, Clang 3.6
>> 
>>  For reference
>>  Compilers by Distribution Version: http://goo.gl/p1t1ls
>> 
>>  C++11 features supported by each compiler:
>>  https://gcc.gnu.org/projects/cxx0x.html
>>  http://clang.llvm.org/cxx_status.html
>> >>>
>> >>
>>
>>
>

Re: Changing Mesos Minimum Compiler Version

[CCAAT]

Hello one and all,

I'm not voting here, my reasons should be ridiculously clear.

I only want to point out that WE, the mesos community, should be
planning to move to gcc-5.x, asap. Why? Excellent question:

[1] https://gcc.gnu.org/wiki/OpenACC

[2] https://gcc.gnu.org/gcc-5/changes.html#offload
(look at the openMP 4.0 specification


Gcc-5.x will allow the beginnings of testing codes on GPUs
and using RDMA; combined these sorts of improvements will
get Mesos + spark + storm "rocking" in the numerical world.

ymmv.
hth,
James




On 04/21/2015 05:07 AM, Alex Rukletsov wrote:

Folks, let's summarize and move on here.

Proposal out on April 9, 2015. Current status (as of April 21, 2015):


+1 (Binding)
--
Vinod Kone
Timothy Chen
Yan Xu
Brenden Matthews

+1 (Non-binding)
--
Cody Maloney
Joris Van Remoortere
Jeff Schroeder
Jörg Schad
Elizabeth Lingg
Alexander Rojas
Alex Rukletsov
Michael Park
Haosdent Huang
Bernd Mathiske

0 (Non-binding)
--
Nikolaos Ballas

There were no -1 votes.

Cody, let's convert MESOS-2604 to an epic and bump the version in 0.23.

Thanks,
Alex


On Mon, Apr 13, 2015 at 12:46 PM, Bernd Mathiske mailto:be...@mesosphere.io>> wrote:

+1

> On Apr 10, 2015, at 6:02 PM, Michael Park mailto:mcyp...@gmail.com>> wrote:
>
 > +1
 >
 > On 9 April 2015 at 17:33, Alexander Gallego mailto:agall...@concord.io>> wrote:
 >
 >> This is amazing for native devs/frameworks.
 >>
 >> Sent from my iPhone
 >>
 >>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere
mailto:jo...@mesosphere.io>>
 >> wrote:
 >>>
 >>> +1
 >>>
  On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney
mailto:c...@mesosphere.io>>
 >> wrote:
  As discussed in the last community meeting, we'd like to bump the
 >> minimum required compiler version from GCC 4.4 to GCC 4.8.
 
  The overall goals are to make Mesos development safer, faster, and
 >> reduce the maintenance burden. Currently a lot of stout has
different
 >> codepaths for Pre-C++11 and Post-C++11compilers.
 
  Progress will be tracked in the JIRA: MESOS-2604
 
  The resulting supported compiler versions will be:
  GCC 4.8, GCC 4.9
  Clang 3.5, Clang 3.6
 
  For reference
  Compilers by Distribution Version: http://goo.gl/p1t1ls
 
  C++11 features supported by each compiler:
  https://gcc.gnu.org/projects/cxx0x.html
  http://clang.llvm.org/cxx_status.html
 >>>
 >>

Re: Changing Mesos Minimum Compiler Version

[Alex Rukletsov]

Folks, let's summarize and move on here.

Proposal out on April 9, 2015. Current status (as of April 21, 2015):


+1 (Binding)
--
Vinod Kone
Timothy Chen
Yan Xu
Brenden Matthews

+1 (Non-binding)
--
Cody Maloney
Joris Van Remoortere
Jeff Schroeder
Jörg Schad
Elizabeth Lingg
Alexander Rojas
Alex Rukletsov
Michael Park
Haosdent Huang
Bernd Mathiske

0 (Non-binding)
--
Nikolaos Ballas

There were no -1 votes.

Cody, let's convert MESOS-2604 to an epic and bump the version in 0.23.

Thanks,
Alex


On Mon, Apr 13, 2015 at 12:46 PM, Bernd Mathiske 
wrote:

> +1
>
> > On Apr 10, 2015, at 6:02 PM, Michael Park  wrote:
> >
> > +1
> >
> > On 9 April 2015 at 17:33, Alexander Gallego  wrote:
> >
> >> This is amazing for native devs/frameworks.
> >>
> >> Sent from my iPhone
> >>
> >>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere 
> >> wrote:
> >>>
> >>> +1
> >>>
>  On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney 
> >> wrote:
>  As discussed in the last community meeting, we'd like to bump the
> >> minimum required compiler version from GCC 4.4 to GCC 4.8.
> 
>  The overall goals are to make Mesos development safer, faster, and
> >> reduce the maintenance burden. Currently a lot of stout has different
> >> codepaths for Pre-C++11 and Post-C++11compilers.
> 
>  Progress will be tracked in the JIRA: MESOS-2604
> 
>  The resulting supported compiler versions will be:
>  GCC 4.8, GCC 4.9
>  Clang 3.5, Clang 3.6
> 
>  For reference
>  Compilers by Distribution Version: http://goo.gl/p1t1ls
> 
>  C++11 features supported by each compiler:
>  https://gcc.gnu.org/projects/cxx0x.html
>  http://clang.llvm.org/cxx_status.html
> >>>
> >>
>
>

Re: Changing Mesos Minimum Compiler Version

[Bernd Mathiske]

+1

> On Apr 10, 2015, at 6:02 PM, Michael Park  wrote:
> 
> +1
> 
> On 9 April 2015 at 17:33, Alexander Gallego  wrote:
> 
>> This is amazing for native devs/frameworks.
>> 
>> Sent from my iPhone
>> 
>>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere 
>> wrote:
>>> 
>>> +1
>>> 
 On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney 
>> wrote:
 As discussed in the last community meeting, we'd like to bump the
>> minimum required compiler version from GCC 4.4 to GCC 4.8.
 
 The overall goals are to make Mesos development safer, faster, and
>> reduce the maintenance burden. Currently a lot of stout has different
>> codepaths for Pre-C++11 and Post-C++11compilers.
 
 Progress will be tracked in the JIRA: MESOS-2604
 
 The resulting supported compiler versions will be:
 GCC 4.8, GCC 4.9
 Clang 3.5, Clang 3.6
 
 For reference
 Compilers by Distribution Version: http://goo.gl/p1t1ls
 
 C++11 features supported by each compiler:
 https://gcc.gnu.org/projects/cxx0x.html
 http://clang.llvm.org/cxx_status.html
>>> 
>> 

Re: Changing Mesos Minimum Compiler Version

[haosdent]

so we have to use devtool in centos 6 now

+1

On Sat, Apr 11, 2015 at 9:53 AM, Cody Maloney  wrote:

> Looking at it again libc++ unfortunately isn't supplied by the apt
> repository, and the libstdc++ from gcc 4.7 is not going to work well /
> cause all sorts of odd incompatibilities.
>
> That means for Debian Wheezy users will have to build GCC 4.8 or 4.9
> themselves in order to build Mesos (Internally I know Mesosphere will be at
> least doing this, we may be able to provide it to others).
>
> On Fri, Apr 10, 2015 at 12:12 PM, Cody Maloney  wrote:
>
>> For Debian Wheezy support the plan is to just use Clang 3.5+ since we can
>> get a modern version of that onto the hosts fairly easily. People are also
>> welcome to compile a newer GCC on the host themselves (honestly not that
>> hard), and setup the extra couple paths needed to ensure it is used when
>> building / running mesos.
>>
>> On Fri, Apr 10, 2015 at 4:09 AM, Nikolaos Ballas neXus <
>> nikolaos.bal...@nexusgroup.com> wrote:
>>
>>>  I have faced the same issue. The only solution is either to use ubuntu
>>> based flavours or red hat based installations. I ping the list of debian
>>> and of course they told me that they don’t plan including it.
>>>   *Nikolaos Ballas*  |  Software Development Manager
>>>   *neXus*
>>>   www.nexusgroup.com 
>>>
>>>
>>>   Twitter: @nmpallas
>>>   Skype: nmpallas
>>>
>>>  On 10 Apr 2015, at 12:54, Alex Rukletsov  wrote:
>>>
>>>  +1 (yes to C++11! — says a software engineer inside me).
>>>
>>>  However, if I read the table correctly, Debian stable has gcc 4.7.2. I
>>> don't think getting gcc >4.8 on Wheezy is a big deal, but I would like have
>>> an idea on how many folks are using Mesos on Wheezy and what do they think
>>> about the change.
>>>
>>> On Fri, Apr 10, 2015 at 12:17 PM, Alexander Rojas <
>>> alexan...@mesosphere.io> wrote:
>>>
 +1 After clearing the RHEL6 issue, I don’t see what are we waiting for

  On 09 Apr 2015, at 23:14, Cody Maloney  wrote:

  As discussed in the last community meeting, we'd like to bump the
 minimum required compiler version from GCC 4.4 to GCC 4.8.

  The overall goals are to make Mesos development safer, faster, and
 reduce the maintenance burden. Currently a lot of stout has different
 codepaths for Pre-C++11 and Post-C++11compilers.

  Progress will be tracked in the JIRA: MESOS-2604

  The resulting supported compiler versions will be:
 GCC 4.8, GCC 4.9
  Clang 3.5, Clang 3.6

  For reference
  Compilers by Distribution Version: http://goo.gl/p1t1ls

  C++11 features supported by each compiler:
 https://gcc.gnu.org/projects/cxx0x.html
 http://clang.llvm.org/cxx_status.html



>>>
>>>
>>
>


-- 
Best Regards,
Haosdent Huang

Re: Changing Mesos Minimum Compiler Version

[Cody Maloney]

Looking at it again libc++ unfortunately isn't supplied by the apt
repository, and the libstdc++ from gcc 4.7 is not going to work well /
cause all sorts of odd incompatibilities.

That means for Debian Wheezy users will have to build GCC 4.8 or 4.9
themselves in order to build Mesos (Internally I know Mesosphere will be at
least doing this, we may be able to provide it to others).

On Fri, Apr 10, 2015 at 12:12 PM, Cody Maloney  wrote:

> For Debian Wheezy support the plan is to just use Clang 3.5+ since we can
> get a modern version of that onto the hosts fairly easily. People are also
> welcome to compile a newer GCC on the host themselves (honestly not that
> hard), and setup the extra couple paths needed to ensure it is used when
> building / running mesos.
>
> On Fri, Apr 10, 2015 at 4:09 AM, Nikolaos Ballas neXus <
> nikolaos.bal...@nexusgroup.com> wrote:
>
>>  I have faced the same issue. The only solution is either to use ubuntu
>> based flavours or red hat based installations. I ping the list of debian
>> and of course they told me that they don’t plan including it.
>>   *Nikolaos Ballas*  |  Software Development Manager
>>   *neXus*
>>   www.nexusgroup.com 
>>
>>
>>   Twitter: @nmpallas
>>   Skype: nmpallas
>>
>>  On 10 Apr 2015, at 12:54, Alex Rukletsov  wrote:
>>
>>  +1 (yes to C++11! — says a software engineer inside me).
>>
>>  However, if I read the table correctly, Debian stable has gcc 4.7.2. I
>> don't think getting gcc >4.8 on Wheezy is a big deal, but I would like have
>> an idea on how many folks are using Mesos on Wheezy and what do they think
>> about the change.
>>
>> On Fri, Apr 10, 2015 at 12:17 PM, Alexander Rojas <
>> alexan...@mesosphere.io> wrote:
>>
>>> +1 After clearing the RHEL6 issue, I don’t see what are we waiting for
>>>
>>>  On 09 Apr 2015, at 23:14, Cody Maloney  wrote:
>>>
>>>  As discussed in the last community meeting, we'd like to bump the
>>> minimum required compiler version from GCC 4.4 to GCC 4.8.
>>>
>>>  The overall goals are to make Mesos development safer, faster, and
>>> reduce the maintenance burden. Currently a lot of stout has different
>>> codepaths for Pre-C++11 and Post-C++11compilers.
>>>
>>>  Progress will be tracked in the JIRA: MESOS-2604
>>>
>>>  The resulting supported compiler versions will be:
>>> GCC 4.8, GCC 4.9
>>>  Clang 3.5, Clang 3.6
>>>
>>>  For reference
>>>  Compilers by Distribution Version: http://goo.gl/p1t1ls
>>>
>>>  C++11 features supported by each compiler:
>>> https://gcc.gnu.org/projects/cxx0x.html
>>> http://clang.llvm.org/cxx_status.html
>>>
>>>
>>>
>>
>>
>

Re: Changing Mesos Minimum Compiler Version

[Joris Van Remoortere]

+1

On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney  wrote:

> As discussed in the last community meeting, we'd like to bump the minimum
> required compiler version from GCC 4.4 to GCC 4.8.
>
> The overall goals are to make Mesos development safer, faster, and reduce
> the maintenance burden. Currently a lot of stout has different codepaths
> for Pre-C++11 and Post-C++11compilers.
>
> Progress will be tracked in the JIRA: MESOS-2604
>
> The resulting supported compiler versions will be:
> GCC 4.8, GCC 4.9
> Clang 3.5, Clang 3.6
>
> For reference
> Compilers by Distribution Version: http://goo.gl/p1t1ls
>
> C++11 features supported by each compiler:
> https://gcc.gnu.org/projects/cxx0x.html
> http://clang.llvm.org/cxx_status.html
>

Changing Mesos Minimum Compiler Version

[Cody Maloney]

As discussed in the last community meeting, we'd like to bump the minimum
required compiler version from GCC 4.4 to GCC 4.8.

The overall goals are to make Mesos development safer, faster, and reduce
the maintenance burden. Currently a lot of stout has different codepaths
for Pre-C++11 and Post-C++11compilers.

Progress will be tracked in the JIRA: MESOS-2604

The resulting supported compiler versions will be:
GCC 4.8, GCC 4.9
Clang 3.5, Clang 3.6

For reference
Compilers by Distribution Version: http://goo.gl/p1t1ls

C++11 features supported by each compiler:
https://gcc.gnu.org/projects/cxx0x.html
http://clang.llvm.org/cxx_status.html