[Rivet] make check failure

[Andy Buckley]

Hi Stefan,

Thanks for reminding me that we have a make check target ;) As Hendrik
mentioned, we don't use it very much and should probably get into the
habit of doing so! Anyway, it should work now.

Andy


Stefan Gieseke wrote:
> Hi Hendrik, 
> 
> ok, that revelaed a missing HepMC.so..., and finally the missing path to 
> RIVETPREFIX/lib
> 
> Adding both manually to the LD_LIBRARY_PATH it works.  
> 
> I.e. running rivet works. 
> 
> Your 'make check', however, still fails:
> 
> ---
> [output of 'make check']
> 
> (...)
> make[2]: Entering directory `/home/stefan/mc/Rivet-1.1.3/plugindemo'
> List of analyses includes MYANALYSIS? NO
> FAIL: testplugin
> ============================================
> 1 of 1 tests failed
> Please report to rivet at projects.hepforge.org
> ============================================
> make[2]: *** [check-TESTS] Error 1
> make[2]: Leaving directory `/home/stefan/mc/Rivet-1.1.3/plugindemo'
> make[1]: *** [check-am] Error 2
> make[1]: Leaving directory `/home/stefan/mc/Rivet-1.1.3/plugindemo'
> make: *** [check-recursive] Error 1
> 
> [PATHs I had to set by hand]
> 
> ~/mc/Rivet-1.1.3 % echo $PYTHONPATH && echo $LD_LIBRARY_PATH 
> /home/stefan/opt/rivet-1.1.3/lib/python2.6/site-packages
> /home/stefan/opt/HepMC-2.04.02/lib:/home/stefan/opt/rivet-1.1.3/lib
> 
> ---
> Anayways, rivet works for me now.  As you said that you didn't know of the 
> 'check' target that current failure might be because the "MYANALYSIS" is 
> outdated. 
> 
> Maybe you want to set the RPATH in the executable as these PATHS should be 
> clear at the configure step.  Something similar should also exist for the 
> PYTHONPATH.  
> 
> Cheers, Stefan 
> 
> 
> On Wed, 8 Jul 2009, Hendrik Hoeth wrote:
> 
>> Thus spake Stefan Gieseke (gieseke at particle.uni-karlsruhe.de):
>>
>>> sorry, I forgot to mention.  I did make sure that the PYTHONPATH is
>>> pointing to a meaningful location.  So, I did "make install" before
>>> make check.  
>>>
>>> The rivet module is also missing if I simply type $RIVET_PREFIX/bin/rivet 
>>> from some location. 
>> Well, calling $RIVET_PREFIX/bin/rivet does exactly the same thing, so
>> it's not a surprise that you get the same error.
>>
>> Do you have $PYTHONPATH/rivet.py and $PYTHONPATH/_rivet.so ?
>>
>> What happens if you go to $PYTHONPATH, run python and do "import rivet"
>> manually?
>>
>>    Hendrik
>>
>> -- 
>> "You have to take the most direct road to go instead of your 
>>  meeting, you have to, this one ended, leave at once the CERN
>>  domain."         (imprint on the CERN visitor ID cards)
>>
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet


-- 
Dr Andy Buckley
Institute for Particle Physics Phenomenology
Durham University
0191 3343798 | 0191 3732613 | www.insectnation.org