You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Robert Stevens <Ro...@mdaus.com> on 2017/08/02 18:35:35 UTC

ExamplesTest.PythonFramework libsvn_delta-1.so.0 path

Hello everyone.  First time in the mailing list here.  Hopefully this is a simple one.  I am trying to run the 'make check' command on a RHEL 7 box that I compiled mesos 1.2.0 with.

Build dir: /tmp/mesos-1.2.0
Src dir: /usr/local/src/mesos-1.2.0
Install dir: /usr/local
Subversion is installed in /usr/local.  Libsvn_delta-1.so.0 is present in /usr/local/lib.
LD_LIBRARY_PATH was set with export pointing to /usr/local/lib.

I ran configure like this:
export LD_LIBRARY_PATH=/usr/local/lib
cd /tmp/mesos-1.2.0
/usr/local/src/mesos-1.2.0/configure --disable-java --with-svn=/usr/local
make -j 16
make -j 16 check

When the python framework test comes around I get a test failed error.  I then run:
bin/mesos-tests.sh --gtest_filter="*.PythonFramework" --verbose

and get the following error:

Traceback (most recent call last):
  File "/usr/local/src/mesos-1.2.0/src/examples/python/test_executor.py", line 25, in <module>
    import mesos.native
  File "build/bdist.linux-x86_64/egg/mesos/native/__init__.py", line 18, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/__init__.py", line 17, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 7, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 6, in __bootstrap__
ImportError: libsvn_delta-1.so.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/local/src/mesos-1.2.0/src/examples/python/test_executor.py", line 25, in <module>
    import mesos.native
  File "build/bdist.linux-x86_64/egg/mesos/native/__init__.py", line 18, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/__init__.py", line 17, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 7, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 6, in __bootstrap__
ImportError: libsvn_delta-1.so.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/local/src/mesos-1.2.0/src/examples/python/test_executor.py", line 25, in <module>
    import mesos.native
  File "build/bdist.linux-x86_64/egg/mesos/native/__init__.py", line 18, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/__init__.py", line 17, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 7, in <module>
  File "build/bdist.linux-x86_64/egg/mesos/scheduler/_scheduler.py", line 6, in __bootstrap__
ImportError: libsvn_delta-1.so.0: cannot open shared object file: No such file or directory


What I don't understand is that libsvn_delta-1.so.0 *is* present in the LD_LIBRARY_PATH:

[root@ip-10-1-55-183 mesos-1.2.0]# echo $LD_LIBRARY_PATH
/usr/local/lib

[root@ip-10-1-55-183 mesos-1.2.0]# ls -lah /usr/local/lib/libsvn_delta-1.*
-rw-r--r--. 1 root root 595K Jun 12 14:07 /usr/local/lib/libsvn_delta-1.a
-rwxr-xr-x. 1 root root 1.1K Jun 12 14:07 /usr/local/lib/libsvn_delta-1.la
lrwxrwxrwx. 1 root root   23 Jun 12 14:07 /usr/local/lib/libsvn_delta-1.so -> libsvn_delta-1.so.0.0.0
lrwxrwxrwx. 1 root root   23 Jun 12 14:07 /usr/local/lib/libsvn_delta-1.so.0 -> libsvn_delta-1.so.0.0.0
-rwxr-xr-x. 1 root root 361K Jun 12 14:07 /usr/local/lib/libsvn_delta-1.so.0.0.0


Its like the python test is not aware of the custom LD_LIBRARY_PATH and thus unable to find the library.  Does anyone have a workaround or fix for this?


Best regards,

Robert Stevens
AWS / DevOps Engineer



1200 Joe Hall Drive / Ypsilanti, MI  48197
Direct: +1 (734) 480-5286
www.mdaus.com

Turning complex data into real-world solutions.





The information contained in this communication is confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system.