[Rivet] swig version not compatible for rivet installation

[Andy Buckley]

On 30/06/13 11:11, Ulla Blumenschein wrote:
> Dear all,
> 
> I  am
> using /afs/cern.ch/atlas/software/releases/17.2.8/gcc-alt-436/x86_64-slc5-gcc43-opt/bin/gcc
> <http://cern.ch/atlas/software/releases/17.2.8/gcc-alt-436/x86_64-slc5-gcc43-opt/bin/gcc>
> and  my PATH
> contains /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt
> <http://cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt> at
> the beginning
> 
> When I install Rivet I get the message:
> checking if
> /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig
> <http://cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig>
> is compatible with the g++ compiler... no
> configure: error: Can't build Python extension since
> /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig
> <http://cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig>
> is not compatible with g++. Get a newer SWIG version!

Hi Ulla,

The Rivet 1.x build system tries to get SWIG to make a Python interface
for a very simple C++ test program, then reports whether or not it was
successful. For some reason it is not being successful with your setup,
but this may be an issue with your environment's compiler setup rather
than SWIG specifically. Can you look in config.log to find the place
where the failure occurs, and post that bit so we have a bit more
information?

Since you obviously have AFS access, is there a reason not to use the
pre-built Rivet installations from
/afs/cern.ch/sw/lcg/external/MCGenerators_lcgcmt*?

Andy

-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Edinburgh / PH Dept, CERN