You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Charles Reiss (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/18 08:12:54 UTC

[jira] [Resolved] (MESOS-125) autoconf/autoreconf version 2.59 does not support option '--no-recursive'

     [ https://issues.apache.org/jira/browse/MESOS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Reiss resolved MESOS-125.
---------------------------------

    Resolution: Fixed

This is no longer a problem since we now distribute a third_party/libprocess which we intend to bootstrap through ./bootstrap and all the rest of third_party doesn't use AC_CONFIG_SUBDIRS.
                
> autoconf/autoreconf version 2.59 does not support option '--no-recursive'
> -------------------------------------------------------------------------
>
>                 Key: MESOS-125
>                 URL: https://issues.apache.org/jira/browse/MESOS-125
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Benjamin Hindman
>            Priority: Blocker
>
> Running our 'bootstrap" script on machines with versions of autoreconf < 2.60 will fail because we use the '--no-recursive' option. It's probably "okay" to turn this option off in the event that it's not supported and just deal with the extra (unnecessary) invocations in the third_party directories.
> Related to this: autoreconf might not function correctly once we include tar.gz packages rather than source directories since we AC_CONFIG_SUBDIRS these directories. I'm not sure the best way to do this, but my gut tells me it would be nice to only unpackage these in the "build" directory, rather than the top level source directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira