[
https://issues.apache.org/jira/browse/MESOS-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499104#comment-14499104
]
haosdent commented on MESOS-2624:
---------------------------------
If user do not have patch in server, the error looks like:
{quote}
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking whether to check for GCC pthread/shared inconsistencies... yes
checking whether -pthread is sufficient with -shared... yes
checking for backtrace in -lunwind... no
checking for patch... no
configure: error: patch command not found in PATH
{quote}
> "configure" should fail when "patch" is not available.
> ------------------------------------------------------
>
> Key: MESOS-2624
> URL: https://issues.apache.org/jira/browse/MESOS-2624
> Project: Mesos
> Issue Type: Improvement
> Reporter: Till Toenshoff
> Assignee: haosdent
> Priority: Minor
> Labels: newbie
>
> Currently {{make}} fails when being used on a rather bare system that does
> not have {{patch}} installed.
> {noformat}
> [...]
> gzip -d -c ../../../../3rdparty/libprocess/3rdparty/libev-4.15.tar.gz | tar
> xf -
> gzip -d -c ../../../../3rdparty/libprocess/3rdparty/boost-1.53.0.tar.gz | tar
> xf -
> test ! -e ../../../../3rdparty/libprocess/3rdparty/libev-4.15.patch || patch
> -d libev-4.15 -p1 <../../../../3rdparty/libprocess/3rdparty/libev-4.15.patch
> /bin/sh: patch: command not found
> Makefile:1570: recipe for target 'libev-4.15-stamp' failed
> make[6]: *** [libev-4.15-stamp] Error 127
> make[6]: *** Waiting for unfinished jobs....
> {noformat}
> The configuration phase should test for the availability of {{patch}} and
> warn the user properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
