gcc - Distutils can't find Python.h -

-

i have distutils setup script extension section, looks this:

from distutils.core import setup, extension  my_module = extension('my_module',                 sources = ['my_file.c', 'my_other_file.c'])  setup (name = 'my_module',        version = '1.0',        description = 'my module',        ext_modules = [my_module])

running setup.py build works fine on mac. when move debian machine, fails:

error: python/python.h: no such file or directory

i have python2.6 , python2.6-dev installed, , file present @ /usr/include/python2.6.

the command executes problem file:

gcc -pthread -fno-strict-aliasing -dndebug -g -fwrapv -o2 -wall -wstrict-prototypes -fpic -i/usr/include/python2.6 -c my_module.c -o -build/xyz/my_module.o

so passing in location of header file.

the obvious difference between mac vs linux environment gcc-4.2 vs gcc-4.4 , python 2.7 vs python 2.6

ideas?

edit:

in c file in question:

#include <python/python.h> #include <python/structmember.h>

may in module, need include "python.h" instead of "python/python.h"?

or may try exporting include path, , try compiling again gcc or g++?

export c_include_path=/usr/include/python2.6:$c_include_path export cplus_include_path=/usr/include/python2.6:$cplus_include_path

Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

c++ - Warning : overflow in implicit constant conversion -

-
in following program, line 5 give overflow warning expected, surprisingly line 4 doesn't give warning in gcc: http://www.ideone.com/u0bxn int main() { int = 256; char c1 = i; //line 4 char c2 = 256; //line 5 return 0; } i thinking both lines should give overflow warning. or there i'm missing? the topic led me experiment this: typedef type checking? there said following(which deleted answer, because when run it, didn't show had expected): //however, you'll warning case: typedef int t1; typedef char t2; t1 x = 256; t2 y = x; //possible overflow warning! (but doesn't give warning :() -wall doesn't include many options. -wconversion 1 of them , warns behavior you're interested in. see http://gcc.gnu.org/onlinedocs/gcc/warning-options.html
Read more