<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Andy, <br>
<blockquote cite="mid:5385C586.9020109@cern.ch" type="cite">
<pre wrap="">
No, not that important but I'm interested to know if it works. Do you
have any clang builds?</pre>
</blockquote>
<br>
Yes, we have
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a aria-describedby="ui-tooltip-17" class="buildinfo"
href="http://cdash.cern.ch/buildSummary.php?buildid=63950"
alt="ctest-2.8.12.2">x86_64-mac109-clang34-opt</a> but yesterday
it did not start because of timeout in Electric Commander.<br>
It is running right now. It will take ~ 1 more hour. I will let you
know.<br>
<br>
<blockquote cite="mid:5385C586.9020109@cern.ch" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">I have same comment as always - why don't you introduce LD_LIBRARY_PATH
and PATH in setenv scripts of Rivet for python which was used for given
build?
</pre>
</blockquote>
<pre wrap="">
Not sure I understand: in my generated rivetenv.sh there is
export PATH="$exec_prefix/bin:/home/andy/heplocal/lib/../bin:$PATH"
export LD_LIBRARY_PATH="${exec_prefix}/lib:/home/andy/heplocal/lib:...
export PYTHONPATH="/home/andy/heplocal/lib/python2.7/site-packages:...
What exactly do you mean about the Python version? It is difficult to
detect the Python installation directories correctly from autotools,
since the installation path decisions are made by Python's own distutils
package.</pre>
</blockquote>
<br>
I am saying that in our installation we remove RPATHs from shared
libraries and in such case in addition to rivetenv.sh one needs to
add python library into LD_LIBARARY_PATH as<br>
well as insert proper PYTHON into PATH to be able to run rivet
executable :)<br>
<br>
Cheers,<br>
Dima<br>
<br>
<br>
</body>
</html>