[Rivet] problem with yaml

[Eike von Seggern]

Hi Robert,

this might be a platform mismatch. Looking at the previous mails I think
you're working on 64bit (see the `x86_64' in the platform tags of e.g.
the gcc directory). However, a 32bit Python version seems to be used
when you try to compile the swig example. There is probably a problem
with the paths setup to find the correct Python version.

tschuess
    eike


On Tue, Feb 01, 2011 at 14:34 +0100, Robert King wrote:
> Hi again,
> 
> I have tried your suggestion and the compiler error is as follows:
> 
> c4_ia32_gcc34/include/python2.5
> In file included from /afs/
> cern.ch/sw/lcg/external/Python/2.5.4p2/slc4_ia32_gcc34/include/python2.5/Python.h:57
> ,
>                  from conftest_wrap.cxx:149:
> /afs/
> cern.ch/sw/lcg/external/Python/2.5.4p2/slc4_ia32_gcc34/include/python2.5/pyport.h:761:2:
> error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
> config?)."
> 
> If you have more suggestions I'd be happy to try them out, but I think I
> have a working solution (use lxplus!) so this isn't high priority.
> 
> Cheers
> 
> Robert
> 
> On 31 January 2011 18:30, Andy Buckley <andy.buckley at ed.ac.uk> wrote:
> 
>> On 31/01/11 17:10, Robert King wrote:
>> > Hi Andy, (& ccd to Rivet list)
>> >
>> > On 31 January 2011 17:30, Andy Buckley <andy.buckley at ed.ac.uk
>> > <mailto:andy.buckley at ed.ac.uk>> wrote:
>> >
>> >     On 31/01/11 16:11, Robert King wrote:
>> >
>> >     Hi again Robert,
>> >
>> >     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.
>> >     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
>> >     <
>> http://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++
>> >     <
>> http://cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt/bin/g++>
>> >     -c
>> >     conftest.i -Wno-format
>> >
>> >
>> > I tried this, but it doesn't like line 1 of conftest.i
>> > conftest.i:1: error: expected unqualified-id before ‘%’ token
>> > Do I need to head this up as a proper C++ code? Sorry if this is
>> > obvious, I'm not sure what we're doing here.
>>
>> Oh, sorry: my cut & paste mistake. Substitute "conftest_wrap.cxx" for
>> "conftest.i" in the C++ compiler command! That file is generated from
>> conftest.i by SWIG: the output should be valid C++, but the input is not ;)
>>
>> You'll find the prototype for this suggestion in the Rivet configure.ac
>> file, which defines the tests that are failing for you.
>>
>> Good luck,
>> Andy
>>
>> --
>> Dr Andy Buckley
>> SUPA Advanced Research Fellow
>> Particle Physics Experiment Group, University of Edinburgh
>>
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>