Mailman 3 pip install numpy throwing a lot of output. - NumPy-Discussion - python.org

newer
number of tests

pip install numpy throwing a lot of output.

older
nditer gurus: is there a more...

Daπid

12 Feb 2013 12 Feb '13

12:37 p.m.

I have just upgraded numpy with pip on Linux 64 bits with Python 2.7, and I got *a lot* of output, so much it doesn't fit in the terminal. Most of it are gcc commands, but there are many different errors thrown by the compiler. Is this expected? I am not too worried as the test suite passes, but pip is supposed to give only meaningful output (or at least, this is what the creators intended). David.

Reply

Sign in to reply online Use email software

Show replies by date

Francesc Alted

12 Feb 12 Feb

1:58 p.m.

On 2/12/13 1:37 PM, Daπid wrote:

I have just upgraded numpy with pip on Linux 64 bits with Python 2.7, and I got *a lot* of output, so much it doesn't fit in the terminal. Most of it are gcc commands, but there are many different errors thrown by the compiler. Is this expected?

Yes, I think that's expected. Just to make sure, can you send some excerpts of the errors that you are getting?

I am not too worried as the test suite passes, but pip is supposed to give only meaningful output (or at least, this is what the creators intended).

Well, pip needs to compile the libraries prior to install them, so compile messages are meaningful. Another question would be to reduce the amount of compile messages by default in NumPy, but I don't think this is realistic (and even not desirable). -- Francesc Alted

Reply

Sign in to reply online Use email software

Daπid

2:18 p.m.

On 12 February 2013 14:58, Francesc Alted wrote:

Yes, I think that's expected. Just to make sure, can you send some excerpts of the errors that you are getting?

Actually the errors are at the beginning of the process, so they are out of the reach of my terminal right now. Seems like pip doesn't keep a log in case of success. The ones I can see are mostly warnings of unused variables and functions, maybe this is the expected behaviour for a library? This errors come from a complete reinstall instead of the original upgrade (the cat closed the terminal, worst excuse ever!): compile options: '-Inumpy/core/include -Ibuild/src.linux-x86_64-2.7/numpy/core/include/numpy -Inumpy/core/src/private -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/include -I/usr/include/python2.7 -Ibuild/src.linux-x86_64-2.7/numpy/core/src/multiarray -Ibuild/src.linux-x86_64-2.7/numpy/core/src/umath -c' gcc: build/src.linux-x86_64-2.7/numpy/core/src/npysort/quicksort.c In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/quicksort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1170:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] In file included from /usr/include/stdlib.h:24:0, from numpy/core/src/npysort/quicksort.c.src:31: /usr/include/features.h:168:0: note: this is the location of the previous definition In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/quicksort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1192:0: warning: "_XOPEN_SOURCE" redefined [enabled by default] In file included from /usr/include/stdlib.h:24:0, from numpy/core/src/npysort/quicksort.c.src:31: /usr/include/features.h:170:0: note: this is the location of the previous definition gcc: build/src.linux-x86_64-2.7/numpy/core/src/npysort/mergesort.c In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/mergesort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1170:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] In file included from /usr/include/stdlib.h:24:0, from numpy/core/src/npysort/mergesort.c.src:31: /usr/include/features.h:168:0: note: this is the location of the previous definition In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/mergesort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1192:0: warning: "_XOPEN_SOURCE" redefined [enabled by default] In file included from /usr/include/stdlib.h:24:0, from numpy/core/src/npysort/mergesort.c.src:31: /usr/include/features.h:170:0: note: this is the location of the previous definition gcc: build/src.linux-x86_64-2.7/numpy/core/src/npysort/heapsort.c In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/heapsort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1170:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] In file included from /usr/include/stdlib.h:24:0, from numpy/core/src/npysort/heapsort.c.src:31: /usr/include/features.h:168:0: note: this is the location of the previous definition In file included from /usr/include/python2.7/pyconfig.h:6:0, from /usr/include/python2.7/Python.h:8, from numpy/core/src/private/npy_sort.h:5, from numpy/core/src/npysort/heapsort.c.src:32: /usr/include/python2.7/pyconfig-64.h:1192:0: warning: "_XOPEN_SOURCE" redefined [enabled by default] compile options: '-Ibuild/src.linux-x86_64-2.7/numpy/core/src/umath -Inumpy/core/include -Ibuild/src.linux-x86_64-2.7/numpy/core/include/numpy -Inumpy/core/src/private -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/include -I/usr/include/python2.7 -Ibuild/src.linux-x86_64-2.7/numpy/core/src/multiarray -Ibuild/src.linux-x86_64-2.7/numpy/core/src/umath -c' gcc: numpy/core/src/umath/umathmodule_onefile.c In file included from numpy/core/src/umath/umathmodule_onefile.c:3:0: numpy/core/src/umath/ufunc_object.c: In function ‘get_ufunc_arguments’: numpy/core/src/umath/ufunc_object.c:717:37: warning: unused variable ‘nout’ [-Wunused-variable] In file included from numpy/core/src/umath/ufunc_object.c:42:0, from numpy/core/src/umath/umathmodule_onefile.c:3: numpy/core/src/umath/umathmodule_onefile.c: At top level: numpy/core/src/private/lowlevel_strided_loops.h:82:1: warning: ‘PyArray_GetStridedCopyFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:97:1: warning: ‘PyArray_GetStridedCopySwapFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:112:1: warning: ‘PyArray_GetStridedCopySwapPairFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:127:1: warning: ‘PyArray_GetStridedZeroPadCopyFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:140:1: warning: ‘PyArray_GetStridedNumericCastFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:151:1: warning: ‘PyArray_GetDTypeCopySwapFn’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:203:1: warning: ‘PyArray_GetDTypeTransferFunction’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:227:1: warning: ‘PyArray_GetMaskedDTypeTransferFunction’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:247:1: warning: ‘PyArray_CastRawArrays’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:296:1: warning: ‘PyArray_TransferNDimToStrided’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:306:1: warning: ‘PyArray_TransferStridedToNDim’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:316:1: warning: ‘PyArray_TransferMaskedStridedToNDim’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:343:1: warning: ‘PyArray_PrepareOneRawArrayIter’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:365:1: warning: ‘PyArray_PrepareTwoRawArrayIter’ declared ‘static’ but never defined [-Wunused-function] numpy/core/src/private/lowlevel_strided_loops.h:389:1: warning: ‘PyArray_PrepareThreeRawArrayIter’ declared ‘static’ but never defined [-Wunused-function] gcc -pthread -shared -Wl,-z,relro build/temp.linux-x86_64-2.7/numpy/core/src/umath/umathmodule_onefile.o -L/usr/lib64 -Lbuild/temp.linux-x86_64-2.7 -lnpymath -lm -lpython2.7 -o build/lib.linux-x86_64-2.7/numpy/core/umath.so building 'numpy.core.scalarmath' extension compiling C sources C compiler: gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC

Reply

Sign in to reply online Use email software

Francesc Alted

2:31 p.m.

On 2/12/13 3:18 PM, Daπid wrote:

On 12 February 2013 14:58, Francesc Alted wrote:

...
Yes, I think that's expected. Just to make sure, can you send some excerpts of the errors that you are getting? Actually the errors are at the beginning of the process, so they are out of the reach of my terminal right now. Seems like pip doesn't keep a log in case of success.

Well, I think these errors are part of the auto-discovering process of the functions supported by the libraries in the hosting OS (kind of `autoconf`for Python), so they can be considered 'normal'.

The ones I can see are mostly warnings of unused variables and functions, maybe this is the expected behaviour for a library? This errors come from a complete reinstall instead of the original upgrade (the cat closed the terminal, worst excuse ever!):

[clip] These ones are not errors, but warnings. While it should be desirable to avoid any warning during the compilation process, not many libraries fulfill this (but patches for removing them are accepted). -- Francesc Alted

Reply

Sign in to reply online Use email software

4084

Age (days ago)

4084

Last active (days ago)

Download

3 comments

2 participants

tags

participants (2)

Daπid
Francesc Alted