Failed to build v1.17.0 on CentOS7 with default gcc (4.8) #14147

xkszltl · 2019-07-29T06:33:51Z

Cannot build numpy v1.17.0 on CentOS 7.
Previous version works fine.
I'm seeing a lot of C99/C11 features in error message, and avx512f.
Not sure if the required --std option is set but I don't think gcc 4.8.5 (the system default compiler on CentOS 7) can handle all of that.

Reproducing code example:

Simply build the wheel on CentOS 7 with python3.

Error message:

Some error log attached.
The entire story is too long to be pasted here.

#6 356.1   compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -c'
#6 356.1   gcc: _configtest.c
#6 356.1   _configtest.c: In function 'main':
#6 356.1   _configtest.c:5:3: warning: implicit declaration of function '__builtin_mul_overflow' [-Wimplicit-function-declaration]
#6 356.1      __builtin_mul_overflow(5, 5, (int*)5);
#6 356.1      ^
#6 356.1   gcc -pthread _configtest.o -o _configtest
#6 356.1   _configtest.o: In function `main':
#6 356.1   /tmp/pip-req-build-poiltggx/_configtest.c:5: undefined reference to `__builtin_mul_overflow'
#6 356.1   collect2: error: ld returned 1 exit status
#6 356.1   failure.
#6 356.1   removing: _configtest.c _configtest.o _configtest.o.d
#6 356.1   C compiler: gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
#6 356.1   
#6 356.1   compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -c'
#6 356.1   gcc: _configtest.c
#6 356.1   _configtest.c: In function 'main':
#6 356.1   _configtest.c:7:16: warning: unused variable 'r' [-Wunused-variable]
#6 356.1      volatile int r = __builtin_cpu_supports("sse");
#6 356.1                   ^
#6 356.1   gcc -pthread _configtest.o -o _configtest
#6 356.1   success!
#6 356.1   removing: _configtest.c _configtest.o _configtest.o.d _configtest
#6 356.1   C compiler: gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
#6 356.1   
#6 356.1   compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -c'
#6 356.1   gcc: _configtest.c
#6 356.1   _configtest.c: In function 'main':
#6 356.1   _configtest.c:7:3: error: Parameter to builtin not valid: avx512f
#6 356.1      volatile int r = __builtin_cpu_supports("avx512f");
#6 356.1      ^
#6 356.1   _configtest.c:7:16: warning: unused variable 'r' [-Wunused-variable]
#6 356.1      volatile int r = __builtin_cpu_supports("avx512f");
#6 356.1                   ^
#6 356.1   failure.
#6 356.1   removing: _configtest.c _configtest.o
#6 356.1   C compiler: gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
#6 356.1   
#6 356.1   compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -c'
#6 356.1   gcc: _configtest.c
#6 356.1   gcc -pthread _configtest.o -o _configtest
#6 356.1   success!
#6 356.1   removing: _configtest.c _configtest.o _configtest.o.d _configtest
#6 356.1   C compiler: gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
#6 356.1   
#6 356.1   compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -c'
#6 356.1   gcc: _configtest.c
#6 356.1   gcc -pthread _configtest.o -o _configtest
#6 356.1   success!
#6 356.1   removing: _configtest.c _configtest.o _configtest.o.d _configtest

#6 358.3     C compiler: gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
#6 358.3     
#6 358.3     compile options: '-Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Inumpy/core/include -Ibuild/src.linux-x86_64-3.6/numpy/core/include/numpy -Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Ibuild/src.linux-x86_64-3.6/numpy/core/src/npymath -Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Ibuild/src.linux-x86_64-3.6/numpy/core/src/npymath -c'
#6 358.3     gcc: build/src.linux-x86_64-3.6/numpy/core/src/npysort/radixsort.c
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_bool':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: note: use option -std=c99 or -std=gnu99 to compile your code
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_bool':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_byte':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_byte':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_ubyte':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_ubyte':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_short':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_short':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_ushort':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_ushort':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_int':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_int':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_uint':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_uint':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_long':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_long':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_ulong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_ulong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_longlong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_longlong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'radixsort_ulonglong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:112:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     numpy/core/src/npysort/radixsort.c.src: In function 'aradixsort_ulonglong':
#6 358.3     numpy/core/src/npysort/radixsort.c.src:202:5: error: 'for' loop initial declarations are only allowed in C99 mode
#6 358.3          for (npy_intp i = 1; i < num; i++) {
#6 358.3          ^
#6 358.3     error: Command "gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Inumpy/core/include -Ibuild/src.linux-x86_64-3.6/numpy/core/include/numpy -Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python3.6m -Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Ibuild/src.linux-x86_64-3.6/numpy/core/src/npymath -Ibuild/src.linux-x86_64-3.6/numpy/core/src/common -Ibuild/src.linux-x86_64-3.6/numpy/core/src/npymath -c build/src.linux-x86_64-3.6/numpy/core/src/npysort/radixsort.c -o build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/numpy/core/src/npysort/radixsort.o -MMD -MF build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/numpy/core/src/npysort/radixsort.o.d" failed with exit status 1
#6 358.3     ----------------------------------------
#6 358.4 ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-poiltggx/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-poiltggx/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-50nzprh1/install-record.txt --single-version-externally-managed --compile Check the logs for full command output.

Numpy/Python version information:

CentOS 7
Default python 3 (3.6)
Default gcc (4.8)

The text was updated successfully, but these errors were encountered:

xkszltl · 2019-07-29T06:36:12Z

Full log attached: numpy.log

eric-wieser · 2019-07-29T07:05:57Z

Numpy 1.17 needs at least --std=c99.

I think the decision was to leave passing that flag up to the distributor rather than doing it automatically, but I forget the rationale. @rgommers, were you part of that discussion?

xkszltl · 2019-07-29T08:34:43Z

That sounds terrible if it's not set by default.
However, it somehow works with Ubuntu 18.04.

Besides, what's the correct way to pass in compiler flags?
I tried export CC="gcc --std=c11" and export CFLAGS="--std=c11" but both were ignored.

See discussion in numpy/numpy#14147

xkszltl · 2019-07-29T09:33:04Z

Looks like on Ubuntu 18.04, gcc 7.4.0 defaults to gnu11 while on CentOS 7, gcc 4.8.5 defaults to gnu90.

I run . scl_source enable devtoolset-8 to switch to gcc 8, which uses gnu17 by default.
But seems all related env vars were ignored by numpy.

xkszltl · 2019-07-29T10:10:37Z

Never mind, numpy can pick up the env correctly.
There's a sudo before pip install which drops everything.

But the issue remains: Do we still have the default support for CentOS 7 and its gcc 4.8.5?

paulofbmarcon · 2019-07-31T14:46:23Z

I don't know if it's related but I got a similar problem trying to install on Amazon Linux. The following work around helped me:
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc48-c99 100 --slave /usr/bin/c89 c89 /usr/bin/gcc48-c89 --slave /usr/bin/c99 c99 /usr/bin/gcc48-c99 --slave /usr/bin/cc cc /usr/bin/gcc48 --slave /usr/bin/gcov gcov /usr/bin/gcov48
update-alternatives --config gcc

sashkab · 2019-07-31T15:24:51Z

@xkszltl You should pass --std=c99 in the CFLAGS environmental variable. Following solved build issues for me.

CFLAGS="--std=c99" python3.6 -mpip wheel "numpy>=1.17,<1.18"

xkszltl · 2019-08-01T01:18:28Z

@sashkab I got it resolved for me by simply using gcc-8. But should --std=c99 be added automatically during build if there's no user setting detected?

antocuni · 2019-08-01T16:48:24Z

numpy 1.17 is also failing to build on pypy, using a ubuntu 14.04 image: https://travis-ci.org/antocuni/pypy-wheels/jobs/566563056

it seems to be that numpy should try harder to compile even on older systems, unless you have a good reason not to.

tylerjereddy · 2019-08-05T03:33:28Z

I think passing in the std flags by default in a compiler and platform-agnostic manner can be tricky & as with many distutils things, hard to test completely.

rgommers · 2019-08-05T16:29:46Z

Numpy 1.17 needs at least --std=c99.

I think the decision was to leave passing that flag up to the distributor rather than doing it automatically, but I forget the rationale. @rgommers, were you part of that discussion?

That rings a bell. I attempted to fix this before, and concluded there's no good place to insert the fix: #12620 (comment). This attempt has some comment as to what the problem is: rgommers@8aaf4d8

Taking a step back, the numpy.distutils design problem we run into here is that all flags are (a) taken over from Python distutils, then hardcoded per compiler in numpy/distutils/<compilername>.py. And at the time we do that hardcoding, we don't know what comes from distutils. And inserting flags dynamically later on (what I tried) is equally tricky.

It's possible I missed a sane way to fix this. Suggestions/PRs welcome.

IIRC the minimum gcc version that works for building numpy at all is 4.8. For gcc <5.1, users need to add --std=c99.

This is a duplicate of gh-12766.

rgommers · 2019-08-06T00:20:11Z

This is biting enough people that I'll mark it for 1.17.1 - should be possible to insert a hacky fix somehow.

charris · 2019-08-06T01:33:48Z

Most linux distributions should have a c99 compiler script that sets the flag

charris@fc [~]$ c99 --version
gcc (GCC) 9.1.1 20190503 (Red Hat 9.1.1-1)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@xkszltl What does that do for you? There ought to be a way we can use that on linux platforms.

xkszltl · 2019-08-06T09:05:18Z

@charris
Good to know! It's part of gcc 4.8.5 rpm in CentOS so I think it should work.
Also available for SCL (I checked devtoolset-6/7/8).

And...Wow you guys already have gcc-9 ?!
Waiting for SCL on CentOS...

xkszltl · 2019-08-06T11:57:13Z

BTW it'll be better if we can find a way to inject $CFLAGS automatically instead of searching for c99 executable as $CC, because $CC may be further customized to gcc-xxx, clang, ccache gcc, distcc...

charris · 2019-08-20T18:17:56Z

Pushed this off to 1.17.2. Tempted to remove the milestone as there is a workaround and the question seems to be "is there a better way."

oolongtea · 2019-08-22T20:30:54Z

Similar issue here on CentOS 7, python 3.6.3+ (configured with --with-pydebug), and gcc 4.8.5. This worked for me when activated into my venv

CFLAGS=-std=c99 pip install numpy==1.17.0

torsava · 2019-08-29T11:16:09Z

This issue also affects RHEL and RHEL container images, pip installing numpy fails on non-intel architectures.

mattip · 2019-11-11T20:12:37Z

Fixed in gh-14771, which added both the flag and a CI run with gcc4.8

sh1ng · 2020-03-18T10:09:59Z

The issue is reproducible on nvidia/cuda-ppc64le:10.0-cudnn7-devel-centos7

mattip · 2020-03-18T10:19:54Z

@sh1ng with what version of NumPy? Are you adding the -std=c99 flag?

sh1ng · 2020-03-18T13:27:57Z

Without adding the flag

Numpy version	Status
1.17.0	Fail
1.17.1	Fail
1.17.2	Fail
1.17.3	Fail
1.17.4	Fail
1.17.5	Fail
1.18.0	Success
1.18.1	Fail
1.18.2	Fail

Adding it do solves the issue, but makes the installation process platform dependent.

sh1ng · 2020-03-18T16:50:33Z

@mattip the issue occurs when miniconda is used, not a centos python package. Most likely conda's issue.

Elham Saremi recently reported the following errors when building Numpy in numpy/core/src/npysort/radixsort.c.src: "error: 'for' loop initial declarations are only allowed in C99 or C11 mode". After some searching, I found Issue 14147[1] on Numpy's main repository about the same problem. As described there, apparently Numpy needs C99 compiler, but doesn't check for it or set it manually (for some strange reason, leaving it to the packagers to check if they want!!!). Any way, after a check with Elham, we were able to fix it by adding the `--std=c99' to CFLAGS of Numpy's build and with this commit, it is now being implemented in the core Maneage to not cause a problem in any other project. [1] numpy/numpy#14147

zoj613 · 2021-08-03T22:00:16Z

So, which 1.17.* version is this flag automatically set so 1.17.* build can be platform independent? I am having trouble building numpy 1.17.0 on 3.8 and 3.9 for CI jobs.

sashkab · 2021-08-03T22:16:58Z

@zoj613 did you try my suggestion above with python 3.8? It worked for me for both 1.16.x and 1.17.x on RHEL/Centos 7.

charris · 2021-08-03T22:20:16Z

@zoj613 It isn't automatically set in any 1.17 version, you need 1.18.0+ for that.

zoj613 · 2021-08-03T22:24:01Z

Ah, Okay. @sashkab 's suggestion seems to work fine on 1.17.3

zevaverbach · 2022-06-08T14:04:19Z

@xkszltl You should pass --std=c99 in the CFLAGS environmental variable. Following solved build issues for me.
CFLAGS="--std=c99" python3.6 -mpip wheel "numpy>=1.17,<1.18"

just to build on this, for anyone that's lost for a next step: pip install <the_wheel_the_above_step_creates>.whl

xkszltl added a commit to xkszltl/Roaster that referenced this issue Jul 29, 2019

Try numpy wheel due to C99 flag requirement in v1.17.0.

4a34b81

See discussion in numpy/numpy#14147

tylerjereddy added the component: build label Aug 5, 2019

rgommers mentioned this issue Aug 6, 2019

Unable to build numpy with GCC 4.8.5 #14182

Closed

rgommers added this to the 1.17.1 release milestone Aug 6, 2019

sh1ng mentioned this issue Aug 9, 2019

Build xgboost with gcc-6.3 h2oai/h2o4gpu#790

Merged

vincentsarago mentioned this issue Aug 15, 2019

numpy 1.17 fails to install RemotePixel/amazonlinux-gdal#25

Open

charris modified the milestones: 1.17.1 release, 1.17.2 release Aug 20, 2019

charris modified the milestones: 1.17.2 release, 1.18.0 release Sep 5, 2019

darrenwiens mentioned this issue Sep 18, 2019

docker build fails developmentseed/sentinel-2-cog#1

Closed

xkszltl added a commit to xkszltl/Roaster that referenced this issue Sep 26, 2019

Patch for numpy C standard issue: numpy/numpy#14147

ded6180

mattip mentioned this issue Oct 15, 2019

Compilation errors #14702

Closed

mattip closed this as completed Nov 11, 2019

mattip mentioned this issue Jan 4, 2020

gcc -std=c99 flag and excess floating point precision handling #15237

Closed

mattip mentioned this issue Aug 16, 2021

MAINT: Drop Python3.7 from supported versions. #19665

Merged

xu-hao added a commit to xu-hao/immcellfie_mvp_mapper that referenced this issue Aug 25, 2021

bump numpy verison see: numpy/numpy#14147

d03c618

xu-hao added a commit to xu-hao/immcellfie_mvp_mapper that referenced this issue Aug 26, 2021

bump numpy verison see: numpy/numpy#14147

6d1220f

xu-hao added a commit to xu-hao/immcellfie_mvp_mapper that referenced this issue Aug 27, 2021

bump numpy verison see: numpy/numpy#14147

ac6b6d4

paiforsyth mentioned this issue Jan 29, 2022

MAINT: Modify setup requirements statsmodels/statsmodels#7993

Merged

3 tasks

Veenarinesingh mentioned this issue Dec 16, 2022

netCDF4 installation requirement has to be updated csyhuang/hn2016_falwa#60

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failed to build v1.17.0 on CentOS7 with default gcc (4.8) #14147

Failed to build v1.17.0 on CentOS7 with default gcc (4.8) #14147

xkszltl commented Jul 29, 2019

xkszltl commented Jul 29, 2019

eric-wieser commented Jul 29, 2019

xkszltl commented Jul 29, 2019

xkszltl commented Jul 29, 2019

xkszltl commented Jul 29, 2019

paulofbmarcon commented Jul 31, 2019 •

edited

sashkab commented Jul 31, 2019 •

edited

xkszltl commented Aug 1, 2019

antocuni commented Aug 1, 2019

tylerjereddy commented Aug 5, 2019

rgommers commented Aug 5, 2019

rgommers commented Aug 6, 2019

charris commented Aug 6, 2019 •

edited

xkszltl commented Aug 6, 2019 •

edited

xkszltl commented Aug 6, 2019 •

edited

charris commented Aug 20, 2019

oolongtea commented Aug 22, 2019

torsava commented Aug 29, 2019

mattip commented Nov 11, 2019

sh1ng commented Mar 18, 2020

mattip commented Mar 18, 2020

sh1ng commented Mar 18, 2020 •

edited

sh1ng commented Mar 18, 2020

zoj613 commented Aug 3, 2021

sashkab commented Aug 3, 2021

charris commented Aug 3, 2021

zoj613 commented Aug 3, 2021

zevaverbach commented Jun 8, 2022

Failed to build v1.17.0 on CentOS7 with default gcc (4.8) #14147

Failed to build v1.17.0 on CentOS7 with default gcc (4.8) #14147

Comments

xkszltl commented Jul 29, 2019

Reproducing code example:

Error message:

Numpy/Python version information:

xkszltl commented Jul 29, 2019

eric-wieser commented Jul 29, 2019

xkszltl commented Jul 29, 2019

xkszltl commented Jul 29, 2019

xkszltl commented Jul 29, 2019

paulofbmarcon commented Jul 31, 2019 • edited

sashkab commented Jul 31, 2019 • edited

xkszltl commented Aug 1, 2019

antocuni commented Aug 1, 2019

tylerjereddy commented Aug 5, 2019

rgommers commented Aug 5, 2019

rgommers commented Aug 6, 2019

charris commented Aug 6, 2019 • edited

xkszltl commented Aug 6, 2019 • edited

xkszltl commented Aug 6, 2019 • edited

charris commented Aug 20, 2019

oolongtea commented Aug 22, 2019

torsava commented Aug 29, 2019

mattip commented Nov 11, 2019

sh1ng commented Mar 18, 2020

mattip commented Mar 18, 2020

sh1ng commented Mar 18, 2020 • edited

sh1ng commented Mar 18, 2020

zoj613 commented Aug 3, 2021

sashkab commented Aug 3, 2021

charris commented Aug 3, 2021

zoj613 commented Aug 3, 2021

zevaverbach commented Jun 8, 2022

paulofbmarcon commented Jul 31, 2019 •

edited

sashkab commented Jul 31, 2019 •

edited

charris commented Aug 6, 2019 •

edited

xkszltl commented Aug 6, 2019 •

edited

xkszltl commented Aug 6, 2019 •

edited

sh1ng commented Mar 18, 2020 •

edited