Build with NPY_SEPARATE_COMPILATION=1 fails

[pv]

Building with

export NPY_SEPARATE_COMPILATION=1
python setup.py build

fails after recent changes (works still in 651ef74):

gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -g build/temp.linux-x86_64-2.7/numpy/core/src/umath/umathmodule.o build/temp.linux-x86_64-2.7/numpy/core/src/umath/reduction.o build/temp.linux-x86_64-2.7/build/src.linux-x86_64-2.7/numpy/core/src/umath/loops.o build/temp.linux-x86_64-2.7/numpy/core/src/umath/ufunc_object.o build/temp.linux-x86_64-2.7/numpy/core/src/umath/ufunc_type_resolution.o -Lbuild/temp.linux-x86_64-2.7 -lnpymath -lm -o build/lib.linux-x86_64-2.7/numpy/core/umath.so
build/temp.linux-x86_64-2.7/numpy/core/src/umath/reduction.o: In function `allocate_reduce_result':
/home/pauli/prj/scipy/numpy/numpy/core/src/umath/reduction.c:48: undefined reference to `PyArray_CreateSortedStridePerm'
/home/pauli/prj/scipy/numpy/numpy/core/src/umath/reduction.c:67: undefined reference to `PyArray_Type'
/usr/bin/ld.bfd.real: build/temp.linux-x86_64-2.7/numpy/core/src/umath/reduction.o: relocation R_X86_64_PC32 against undefined hidden symbol `PyArray_Type' can not be used when making a shared object
/usr/bin/ld.bfd.real: final link failed: Bad value
collect2: ld returned 1 exit status
build/temp.linux-x86_64-2.7/numpy/core/src/umath/reduction.o: In function `allocate_reduce_result':
/home/pauli/prj/scipy/numpy/numpy/core/src/umath/reduction.c:48: undefined reference to `PyArray_CreateSortedStridePerm'
/home/pauli/prj/scipy/numpy/numpy/core/src/umath/reduction.c:67: undefined reference to `PyArray_Type'
/usr/bin/ld.bfd.real: build/temp.linux-x86_64-2.7/numpy/core/src/umath/reduction.o: relocation R_X86_64_PC32 against undefined hidden symbol `PyArray_Type' can not be used when making a shared object
/usr/bin/ld.bfd.real: final link failed: Bad value
collect2: ld returned 1 exit status

Time to scrap the one-file build?

[thouis]

I'm +1 on making separate compilation the default, if I get a vote.

[cournape]

I would be ok making +1 the default iif we have a buildbot on unix for the one file build. Some platforms may not have the necessary features for the one file build, and it would be a shame to drop support just for this.

OTOH, I think supporting the one file mode should be quite easy if separate mode is the default than the opposite.

[cournape]

I am working on a branch to test the separate compilation mode on travis (and fix the issues of course).: http://travis-ci.org/#!/cournape/numpy

[seberg]

Travis is testing both now, and it is the default. So closing this.