On Sun, Nov 2, 2014 at 10:32 PM, Andreas Enge <andr...@enge.fr> wrote: > With the new python wrapper, something is found: > checking for python3-config... python3-config > checking for Python 3.x prefix... > /gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5 > checking for Python 3.x exec-prefix... > /gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5 > checking for Python 3.x version... python3.3 > checking for Python 3.x lib dir... lib > checking for Python 3.x header files... > -I/gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5/include/python3.3m > -I/gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5/include/python3.3m > checking for Python 3.x library... Not found > > Whatever this means! The header files are correctly located in the python3.3m > subdirectory of the include directory. However, the CPATH includes only > the include/ directory itself (logic!). And apparently the tests do not > use the correct include path. > > Could maybe a swig specialist have a look?
I've just noticed the following sentence in the release of version 2.0.12: - Compilation fixes on some systems for the generated Lua, PHP, Python and R wrappers. See http://www.swig.org/ Maybe, it was an upstream bug? Regards, Fede
