In order to better evaluate the current position of developers with respect
to autotools versions, is there a way we can do an informal poll to see how
many people are still using automake 1.11 or 1.12? If it's only a small
number of people, we can try to find an upgrade path for their
On Fri, Jun 26, 2015 at 1:38 AM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Taking a step back, it looks like the patches in MESOS-2273 approached the
problem assuming 1.13. Have you re-considered how you might approach it if
you didn't have 1.13? Or is this 1.13 macro the only solution?
On Jun 25, 2015, at 11:01 PM, Kapil Arya ka...@mesosphere.io wrote:
On Fri, Jun 26, 2015 at 1:38 AM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Taking a step back, it looks like the patches in MESOS-2273 approached the
problem assuming 1.13. Have you re-considered how you might
Taking a step back, it looks like the patches in MESOS-2273 approached the
problem assuming 1.13. Have you re-considered how you might approach it if
you didn't have 1.13? Or is this 1.13 macro the only solution?
Worth noting that users can already build the tests without running them by
What about CentOS 5 and 6?
https://en.wikipedia.org/wiki/CentOS#End-of-support_schedule
Also, how does this interact with the effort to use CMake?
https://issues.apache.org/jira/browse/MESOS-898
On Thu, Jun 25, 2015 at 10:40 AM, Kapil Arya ka...@mesosphere.io wrote:
Hi All,
First off, I am
Hi All,
First off, I am not sure if we record the minimum required version of
automake/autoconf somewhere in the documentation.
Having said that, I want to propose to move to automake 1.13 in order to be
able to use the AM_EXTRA_RECURSIVE_TARGETS macro which allows us to add a
test target to
we encountered a lot of issues in thrift between all the backwards
incompatible changes automake had in 1.12 to 1.14 and trying to support all
the default versions across different distros. due to this we are switching
to cmake as well
-Jake
On Thu, Jun 25, 2015 at 1:46 PM, Benjamin Mahler
It's not available for CentOS 5/6 or the previous debian stable. I guess
since we still want to keep supporting the older distros, one possibility
is to create a patch for configure.ac which is applied during ./bootstrap
after detecting the automake version. Is this an acceptable solution?
If
CentOS 5 and 6 don't come out of the box with a new enough version of GCC
to compile Mesos. Already they need to upgrade that to compile Mesos. I
don't see how adding another upgrade when they have to do GCC is overly
onerous / should require lots of compatibility hacks to make unnecessary.
On
On Thu, Jun 25, 2015 at 3:27 PM, Cody Maloney c...@mesosphere.io wrote:
CentOS 5 and 6 don't come out of the box with a new enough version of GCC
to compile Mesos. Already they need to upgrade that to compile Mesos. I
don't see how adding another upgrade when they have to do GCC is overly
Apparently, there is a way to get latest the autotools on CentOS 5 through
the same community that provides devtoolset:
https://www.softwarecollections.org/en/scls/praiskup/autotools/
If the tools are available, would there be any other objections to move to
the newer versions?
On Thu, Jun
Well, CentOS 5 users don't have to upgrade gcc, they can use devtoolset-2.
However, devtoolset-2 doesn't provide the newer automake FWICT.
On Thu, Jun 25, 2015 at 3:38 PM, Marco Massenzio ma...@mesosphere.io
wrote:
On Thu, Jun 25, 2015 at 3:27 PM, Cody Maloney c...@mesosphere.io wrote:
12 matches
Mail list logo
