[Rivet] Rivet 2.1.2 and YODA 1.0.7 for pre-release testing

[Dmitri Konstantinov]

Hi Andy,

The build with clang is fine. I have checked all log files as well. 
Nothing suspicious.

Cheers,
       Dima

On 5/28/14 1:30 PM, Dmitri Konstantinov wrote:
> Hi Andy,
>> No, not that important but I'm interested to know if it works. Do you
>> have any clang builds?
>
> Yes, we have x86_64-mac109-clang34-opt 
> <http://cdash.cern.ch/buildSummary.php?buildid=63950> but yesterday it 
> did not start because of timeout in Electric Commander.
> It is running right now. It will take ~ 1 more hour. I will let you know.
>
>>> 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?
>> 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.
>
> 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
> well as insert proper PYTHON into PATH to be able to run rivet 
> executable :)
>
> Cheers,
>       Dima
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20140528/9c18d406/attachment.html>