Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mesos-dev@incubator.apache.org
Date: Wed, 1 Feb 2012 01:04:56 +0000 (UTC)
From: "Benjamin Hindman (Closed) (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: <905868303.868.1328058296837.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1666404536.1006.1327685655217.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (MESOS-138) When running Make (right at the end) it
 tries to copy mesos.py to a different directory, but the two directories
 are the same, so it fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Hindman closed MESOS-138.
----------------------------------

    Resolution: Fixed
      Assignee: Benjamin Hindman
    
> When running Make (right at the end) it tries to copy mesos.py to a different directory, but the two directories are the same, so it fails
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-138
>                 URL: https://issues.apache.org/jira/browse/MESOS-138
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>         Environment: Red Hat (Amazon's AMI)
>            Reporter: Matthew Rathbone
>            Assignee: Benjamin Hindman
>            Priority: Minor
>              Labels: build-failure, python
>
> This bug is present in the generated Makefile.in (I ran ./configure.template.amazon-linux-64)
> The error is something like 'cp failed, the source and destination directories are the same'
> When you see the error, deleting this line from src/Makefile.in will fix it:
> @HAS_PYTHON_TRUE@      @cp -pf $(srcdir)/python/src/mesos.py python/src/mesos.py

--
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