Build fails on OS X (python setup.py build_ext --inplace)

Issue #6 resolved
Will Dabney created an issue

Updated to latest sources and trying to compile the modules with,

python setup.py build_ext --inplace

Output is:

gcc-4.2 not found, using clang instead skipping 'Representations/FastCythonKiFDD.cpp' Cython extension (up-to-date) building 'Representations.FastCythonKiFDD' extension clang -fno-strict-aliasing -fno-common -dynamic -isysroot /Developer/SDKs/MacOSX10.6.sdk -arch i386 -arch x86_64 -g -O2 -DNDEBUG -g -O3 -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include -IRepresentations -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c Representations/FastCythonKiFDD.cpp -o build/temp.macosx-10.6-intel-2.7/Representations/FastCythonKiFDD.o -std=c++11 In file included from Representations/FastCythonKiFDD.cpp:322: In file included from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include/numpy/arrayobject.h:15: In file included from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:17: In file included from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: warning: "Using deprecated NumPy API, disable it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings] #warning "Using deprecated NumPy API, disable it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" ^ In file included from Representations/FastCythonKiFDD.cpp:324: Representations/FastKiFDD.h:3:10: fatal error: 'array' file not found #include <array> ^ 1 warning and 1 error generated. error: command 'clang' failed with exit status 1

Comments (4)

  1. Will Dabney reporter

    It looks like the necessary includes for C++ libraries are not being added to the compile command.

  2. Will Dabney reporter

    More looking into it, and I think it is just due to having an older version of gcc/g++/clang.

  3. Log in to comment