[Rivet] Rivet 1.1.3 release today - please test!

[Andy Buckley]

James Monk wrote:
> 
> On 8 Jun 2009, at 10:59, Andy Buckley wrote:
> 
>> I'd also like people to try the new and shiny bootsrap script, which is 
>> a lot friendlier and more robust than the old one:
>> http://svn.hepforge.org/rivet/bootstrap/rivet-bootstrap.py
>> (the name will be changing, and the other variants deleted, on release)
> 
> I still had that problem where it tried to use my existing Rivet 
> installation (with the broken fastjet ee_kt alg) to generate the latex. 
>  Since that failed I didn't get anything in the local/bin directory 
> (although rivet had built in its build dir).  When I removed my existing 
> Rivet installation I get during the latex generation:
> 
> ImportError: 
> dlopen(/Users/jmonk/Physics/Rivet-test/build/Rivet-1.1.3b0/pyext/build/lib.macosx-10.5-i386-2.5/_rivet.so, 
> 10): Library not loaded: 
> /Users/jmonk/Physics/Rivet-test/local/lib/libRivet.5.dylib 
> Referenced from: 
> /Users/jmonk/Physics/Rivet-test/build/Rivet-1.1.3b0/pyext/build/lib.macosx-10.5-i386-2.5/_rivet.so  
> 
> Reason: image not found
> 
> Ignoring the incorrect .so extension on the python _library it looks to 
> me like the installer is trying to generate latex from the installed 
> version of Rivet before it has installed it - libRivet.5.dylib is 
> present in the build area but has not been installed by this point.  Can 
> the order be changed so that the documentation is generated after the 
> libraries have been installed?

I tried, but it's certainly not easy: you have to do a lot of autotools 
stuff manually, including managing the data install/uninstall steps. I'd 
rather not go there if there's an alternative (and it's nice to be able 
to produce the docs without installing)

However, what is done at the moment is a bit cleverer than just assuming 
that there is an existing Rivet: the doc-generating scripts attempt to 
set the PYTHONPATH and library path to point at the uninstalled copies 
of the libraries. It works for me, and the other Linux people who've 
tested it, but the .so instead of .dylib issue could be breaking it for 
you. Also, I'm setting LD_LIBRARY_PATH, having forgotten that on Macs 
it's DYLD_LIBRARY_PATH. Can you try hacking these things on your copy 
and see if it can be made to work?

Andy

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