|
[Rivet] problem with yamlBen Waugh waugh at hep.ucl.ac.ukMon Jan 31 16:39:58 GMT 2011
Hi Robert, On 31/01/11 16:30, Andy Buckley wrote: > On 31/01/11 16:11, Robert King wrote: >> configure:17305: checking for Python include path >> configure:17308: result: /afs/cern.ch/sw/lcg/external/Python/2.5.4p2/slc4_ia32_gcc34/include/python2.5 >> configure:17328: checking for swig >> configure:17346: found /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig >> configure:17358: result: /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig >> configure:17443: checking if /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig can make a Python function wrapper >> configure:17447: result: yes >> configure:17461: checking if the /afs/cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt/bin/g++ compiler accepts the -Wno-format flag >> configure:17477: result: yes >> configure:17481: adding -Wno-format to swig compilation test >> configure:17495: checking if /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig is compatible with the /afs/cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt/bin/g++ compiler >> configure:17501: result: no >> configure:17504: error: Can't build Python extension since /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig is not compatible with /afs/cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt/bin/g++. Get a newer SWIG version! > > The lines above are the relevant ones from your config.log file -- it > looks like SWIG is working but is not compatible with your C++ compiler. In case it helps, when I last installed Rivet on our SLC5 cluster I found it useful to source the following script to ensure a compatible set of compilers etc. in my $PATH: source /afs/cern.ch/sw/lcg/contrib/gcc/4.3/x86_64-slc5-gcc43-opt/setup.sh Cheers, Ben > As I don't have that compiler I can't check, but if you want to chase it > up, try doing a manual test of SWIG with a mini interface file. The test > being run by the configure script in your case is roughly to make a file > called conftest.i, containing the following: > > %module conftest > %{ > void foo(); > %} > void foo(); > > > Then run > > /afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig > -c++ -python conftest.i > > and then > > /afs/cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt/bin/g++ -c > conftest.i -Wno-format > -I/afs/cern.ch/sw/lcg/external/Python/2.5.4p2/slc4_ia32_gcc34/include/python2.5 > > There are a few extra flags which are being added to the compiler by > Rivet, but those should hopefully not be important for this test. > Presumably the C++ compiler is working for everything else... I'd be > interested to know if this works, and if not what the compiler error > message is in the final step. > > Best wishes, > Andy > -- Dr Ben Waugh Tel. +44 (0)20 7679 7223 Dept of Physics and Astronomy Internal: 37223 University College London London WC1E 6BT
More information about the Rivet mailing list |