You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/03/05 00:05:14 UTC

[jira] [Resolved] (MESOS-340) Gperftools target always rebuilds.

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

Benjamin Mahler resolved MESOS-340.
-----------------------------------

    Resolution: Fixed
    
> Gperftools target always rebuilds.
> ----------------------------------
>
>                 Key: MESOS-340
>                 URL: https://issues.apache.org/jira/browse/MESOS-340
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>
> From make --debug=v:
>       Considering target file `gperftools-2.0/libprofiler.la'.
>         Considering target file `gperftools-2.0-stamp'.
>           Considering target file `gperftools-2.0.tar.gz'.
>            Finished prerequisites of target file `gperftools-2.0.tar.gz'.
>           No need to remake target `gperftools-2.0.tar.gz'; using VPATH name `../../third_party/gperftools-2.0.tar.gz'.
>          Finished prerequisites of target file `gperftools-2.0-stamp'.
>          Prerequisite `../../third_party/gperftools-2.0.tar.gz' is older than target `gperftools-2.0-stamp'.
>         No need to remake target `gperftools-2.0-stamp'.
>        Finished prerequisites of target file `gperftools-2.0/libprofiler.la'.
>        Prerequisite `gperftools-2.0-stamp' is newer than target `gperftools-2.0/libprofiler.la'.
>       Must remake target `gperftools-2.0/libprofiler.la'.
> cd gperftools-2.0 && ./configure  --enable-shared=no --with-pic --srcdir=. && \
> 	  make 
>       Commands of `gperftools-2.0/libprofiler.la' are being run.
> I will look at adding a build-stamp target similar to what we have for protobuf. (see: third_party/Makefile.am)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira