[Bf-committers] solving the issues of switching to python 2.4on
Os X for next release
Hans Lambermont
hans at lambermont.dyndns.org
Fri Aug 26 13:29:13 CEST 2005
Gilbert, Joseph wrote:
> Python.h should always be declared before anything else because it sucks
> in a bunch of standard library headers. I don't know if this is your
> problem or not. Also I remember that <iostream.h> is not kosher for
> c++. Prob should change this to <iostream>.
>
> #include "Python.h"
> #include <vector>
> #include <iostream>
>
> might be better.
Changing iostream.h to iostream does not help :
g++ -I /usr/local/include/python2.4 a.c
In file included from /usr/include/c++/3.4/ios:48,
from /usr/include/c++/3.4/ostream:45,
from /usr/include/c++/3.4/iostream:45,
from a.c:3:
/usr/include/c++/3.4/bits/localefwd.h:58:34: macro "isspace" passed 2 arguments, but takes just 1
In file included from /usr/include/c++/3.4/ios:48,
from /usr/include/c++/3.4/ostream:45,
from /usr/include/c++/3.4/iostream:45,
from a.c:3:
/usr/include/c++/3.4/bits/localefwd.h:58: error: `std::isspace' declared as an `inline' variable
...
And changing the include *order* is not easy, these 3 include files are the
result of several other includes. See my earlier posts.
-- Hans
More information about the Bf-committers
mailing list