Manta Interactive Ray Tracer Development Mailing List

Text archives Help


[Manta] Re: Re: python error from swig, pycallback.cc


Chronological Thread 
  • From: Aaron Knoll < >
  • To:
  • Subject: [Manta] Re: Re: python error from swig, pycallback.cc
  • Date: Mon, 30 Jun 2008 09:50:33 -0600
Hi guys -- the issue isn't python linkage; I found the path to libpython2.5.a on the LLNL end and I get the same compile error (anyway, it's a compile, not a link error).

I would assume this is a compiling issue; however the odd part is that hex and the LLNL machine have the same gcc version (4.1.2). As I mentioned before, they have the same swig version as well.

Any ideas what might cause this problem?

-Aaron

On Jun 30, 2008, at 9:42 AM, Aaron Knoll wrote:

Err... I meant the .so is dynamic, and .a is static!
-Aaron

On Jun 30, 2008, at 9:27 AM, Aaron Knoll wrote:

Hi guys,

When compiling Manta on a LLNL machine, I had to use their staticly linked library (libpython2.5.so) as opposed to the dynamic library (libpython2.5.a) typically used by Manta.

When doing this, I get compile errors as follows:

Building CXX object Interface/CMakeFiles/Manta_Interface.dir/ Context.o
/g/g23/knolla/Manta/build/SwigInterface/pycallbackPYTHON_wrap.cxx: In function 'int SWIG_Python_ConvertFunctionPtr(PyObject*, void**, swig_type_info*)':
/g/g23/knolla/Manta/build/SwigInterface/pycallbackPYTHON_wrap.cxx: 2051: error: invalid conversion from 'const char*' to 'char*'

Is there an easy way to fix this in pycallback.cc, as opposed to getting LLNL to install libpython2.5.a on their end?

Thanks!

Aaron


Archive powered by MHonArc 2.6.16.

Top of page