[Rivet] Yaml error in newest Rivet

[Christian Roehr]

Hi Hendrik and Andy,

thank you very much for your help. Indeed, that solved my problem!

"make install" in the yaml-cpp directory copied the yaml libs and
headers into the prefix directory. "configure" then could find them
there (WITHOUT specifying the yaml paths by any of the --*yaml*
options). Launching "make" again then worked, also in the bin directory,
where the error was thrown before.

I found out now, that the problem was most probably connected to shell
environment variables (LD_LIBRARY_PATH, PATH, PYTHONPATH,
RIVET_ANALYSIS_PATH, RIVET_REF_PATH, RIVET_INFO_PATH) to be set wrongly.
All these variables contained paths to my previous Rivet installation
(1.2.1), which probably caused that error somehow. Cleaning out these
variables solves the problem completely, I cannot reproduce the error
anymore.

So, this was a problem of my system. All the more thank you guys for
helping me with that!

Cheers,
Christian



On Thu, 21 Oct 2010, Andy Buckley wrote:

> On 20/10/10 19:25, Hendrik Hoeth wrote:
>> Moin Christian,
>>
>> Thus spake Christian Roehr (roehr at particle.uni-karlsruhe.de):
>>>
>>> The configure script could not find yaml-cpp on my system (cf. the
>>> output of configure attached to this mail) and stated that Rivet will
>>> build this library itself.  Indeed, that bit seems to be working,
>>> "make" in tools/yaml-cpp seems to run through properly.
>>
>> Have you tried running "make install" in tools/yaml-cpp before running
>> "make" again in the main rivet directory? Just a guess, hoping that the
>> linker will then pick up libyaml in the install directory.
>
> Thanks Hendrik. Yes, that's worth a try in case the first install has
> somehow botched. I see clean builds on all platforms I've tried where
> yaml-cpp is not pre-installed, so I'm not sure what's going wrong here.
>
> Andy
>
> -- 
> Dr Andy Buckley
> SUPA Advanced Research Fellow
> Particle Physics Experiment Group, University of Edinburgh
>