using cmake too, but that said, it
>is very new. If you have any problems or issues, we'd love to hear about
>it!
>
>/Jeff
>
>-Original Message-
>From: Wood, Aaron [mailto:aaron.w...@verizon.com]
>Sent: Thursday, June 22, 2017 8:28 AM
>To: dev@mesos.apache.org
>S
et, so the CMake output is kind of stuck in "developer mode"
>> and it won't generate an installable package.
>>
>> I probably would not yet recommend the CMake build system for production
>> use.
>>
>> As far as what features are missing, I'm not aware o
Hi all,
I'm curious as to what the current state of came is on Linux. I noticed that
some features that are present in the autotools build are not yet in cmake.
Also, the output from a successful cmake build looks a bit different as far as
the number of libraries that are produced and the
check to configure.ac anyways to
>> warn people if their compiler doesn't support this option, would it be
>> an option to use -fstack-protector-strong on compilers that support it
>> and -fstack-protector otherwise?
>>
>> Best regards,
>> Benno
>>
>>
Werror` is somewhat
>of an anti-pattern, it just seems to guarantee that the build will break
>whenever the compiler writers decide to add a new warning in the future,
>or when someone tries building with another compiler.
>
>Best regards,
>Benno
>
>On 10.10.2016 20:07, W
Hi everyone,
I am proposing that Mesos requires GCC >= 4.9 going forward instead of >=
4.8.1. This is mainly to support -fstack–protector-strong.
See the related RR here https://reviews.apache.org/r/52645/
How does everyone feel about this?
Thanks,
Aaron
