Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
It seems we're starting to get Travis-CI failures in test_cython.py. Example here:
----------------------------- Captured stdout call ----------------------------- Compiling pyarrow_cython_example.pyx because it changed. [1/1] Cythonizing pyarrow_cython_example.pyx running build_ext building 'pyarrow_cython_example' extension creating build creating build/temp.linux-x86_64-2.7 gcc -fno-strict-aliasing -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O3 -pipe -fdebug-prefix-map=${SRC_DIR}=/usr/local/src/conda/${PKG_NAME}-${PKG_VERSION} -fdebug-prefix-map=${PREFIX}=/usr/local/src/conda-prefix -DNDEBUG -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/travis/build/apache/arrow/pyarrow-test-2.7/lib/python2.7/site-packages/numpy/core/include -I/home/travis/build/apache/arrow/python/pyarrow/include -I/home/travis/build/apache/arrow/pyarrow-test-2.7/include/python2.7 -c pyarrow_cython_example.cpp -o build/temp.linux-x86_64-2.7/pyarrow_cython_example.o -std=c++11 ----------------------------- Captured stderr call ----------------------------- gcc: error: unrecognized command line option '-fno-plt' error: command 'gcc' failed with exit status 1
(from https://travis-ci.org/apache/arrow/jobs/498722197)
I'm afraid this looks like a conda-forge toolchain issue
Attachments
Issue Links
- links to