[Adonthell-devel] compiling v0.4 on OS X

[Kai Sterker]

I finally made another attempt to compile the new code under OS X. 
However, it doesn't like the new python/callback class much:

 g++ -DHAVE_CONFIG_H -I. -I../.. -I../../libltdl 
-I/usr/include/python2.2 -g -Wall -fno-exceptions -fno-rtti 
-I../../src/ -MT libadonthell_python_la-python.lo -MD -MP -MF 
.deps/libadonthell_python_la-python.Tpo -c python.cc  -fno-common -o 
.libs/libadonthell_python_la-python.o
../../src/base/callback.h: In constructor 
`base::membertranslator_0<Callee,
   MemFunc>::membertranslator_0(Callee&, const MemFunc&) [with Callee =
   python::functor_0, MemFunc = void (python::functor_0::*)()]':
../../src/base/callback.h:98:   instantiated from 
`base::membertranslator_0<Callee, MemFunc>::membertranslator_0(Callee&, 
const MemFunc&) [with Callee = python::functor_0, MemFunc = void 
(python::functor_0::*)()]'
../../src/python/callback.h:68:   instantiated from here
../../src/base/callback.h:98: could not convert `m' to `void
   (python::functor_0::*&)()'
../../src/base/callback.h:98: in passing argument 3 of `
   base::membertranslator_0<Callee, 
MemFunc>::membertranslator_0(Callee&, const
   MemFunc&) [with Callee = python::functor_0, MemFunc = void
   (python::functor_0::*)()]'
../../src/base/callback.h: In constructor 
`base::membertranslator_0<Callee,
   MemFunc>::membertranslator_0(Callee&, const MemFunc&) [with Callee =
   python::functor_0, MemFunc = void (python::functor_0::*)()]':
../../src/base/callback.h:98: could not convert `m' to `void
   (python::functor_0::*&)()'
../../src/base/callback.h:98: in passing argument 3 of `
   base::membertranslator_0<Callee, 
MemFunc>::membertranslator_0(Callee&, const
   MemFunc&) [with Callee = python::functor_0, MemFunc = void
   (python::functor_0::*)()]'
make[3]: *** [libadonthell_python_la-python.lo] Error 1

I don't really see what the problem is, especially since the rest of 
that file compiles fine. Is there a difference between the call in line 
68 and those in 97 respectively 132?

Any ideas?

Kai

P.S. Maybe I go ahead and see whether I can obtain a newer gcc. 
Obviously, the one shipped by Apple (gcc 3.1 20020420) seems to have 
its problems.