[ 
https://issues.apache.org/jira/browse/MESOS-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314860#comment-14314860
 ] 

Hans van den Bogert commented on MESOS-2202:
--------------------------------------------

I thought this solved my problems, however, running spark in CoarseGrained mode 
creates a problem.

In my case, I compile on a cluster head node, which has the devel packages. Now 
if I want to run on a compute node, the "make-installed"-ed mesos still refers 
to libapr*.so packages which are only in the devel-packages (in contrast to 
libapr*.so.0 which are in the non-devel packages).

The RPATH in the actual binaries are fine, but it are the helper scripts like 
$PREFIX/bin/master.sh who change the RPATHs on the fly (if I'm correct). Now 
this wouldn't really be a problem, cause one can simply run e.g. 
MESOS_HOME/build/src/.libs/lt-mesos-master directly, this doesn't work in all 
cases

Now the question is, am I wrong in to expect that an autoconf based package 
like mesos, shouldn't rely on devel packages once compilation is done?

Example error when running on compute node:
bin/mesos-master.sh
g++: /usr/lib64/libaprutil-1.so: No such file or directory
g++: /usr/lib64/libapr-1.so: No such file or directoryn

> Centos install needs additional package
> ---------------------------------------
>
>                 Key: MESOS-2202
>                 URL: https://issues.apache.org/jira/browse/MESOS-2202
>             Project: Mesos
>          Issue Type: Documentation
>          Components: documentation
>    Affects Versions: 0.21.0
>         Environment: Clean centos 6.5 server install
>            Reporter: Hans van den Bogert
>            Assignee: Palak Choudhary
>            Priority: Minor
>
> The install documentation on:
> http://mesos.apache.org/gettingstarted/ is not complete for Centos, an 
> additional package is needed: 
> *apr-utils-devel*
> Thus:
> bq. sudo yum install -y python-devel java-1.7.0-openjdk-devel zlib-devel 
> libcurl-devel openssl-devel cyrus-sasl-devel cyrus-sasl-md5 apr-devel 
> subversion-devel apr-utils-devel



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to