/root/build-platform/prj_rgos/images/host/usr/bin/mips64-octeon-linux-gnu-gcc

lrwxrwxrwx 1 root root 33 Apr 29 14:31 mips64-octeon-linux-gnu-gcc -> mips64-octeon-linux-gnu-gcc-4.7.0 -rwxr-xr-x 1 root root 1976468 Apr 29 14:31 mips64-octeon-linux-gnu-gcc-4.7.0

CC networking.o networking.c:3204:9: error: expected '=', ',', ';', 'asm' or 'attribute' before 'unsigned' networking.c: In function 'IOThreadMain': networking.c:3225:17: error: 'io_threads_pending' undeclared (first use in this function) networking.c:3225:17: note: each undeclared identifier is reported only once for each function it appears in networking.c: In function 'initThreadedIO': networking.c:3279:9: error: 'io_threads_pending' undeclared (first use in this function) networking.c: In function 'handleClientsWithPendingWritesUsingThreads': networking.c:3364:9: error: 'io_threads_pending' undeclared (first use in this function) networking.c: In function 'handleClientsWithPendingReadsUsingThreads': networking.c:3451:9: error: 'io_threads_pending' undeclared (first use in this function) Makefile:679: recipe for target 'networking.o' failed make[4]: *** [networking.o] Error 1

Comment From: xiaozhitaba

use sig_atomic_t to resolve compile error

Comment From: xiaozhitaba

@antirez

Comment From: antirez

Hello @xiaozhitaba, we started requiring a C11 compiler starting with Redis 6, so that we can freely use C11 features, especially _Atomic with well defined semantics, in every place of Redis. People with very old compilers can still use Redis 5 that is still supported.

Comment From: oranagra

@xiaozhitaba which OS where you using? p.s. this is partially a dup of #6286 (with the exception that the main discussion there is about Centos 7)

Comment From: oranagra

Update: The core team have decided to step back from the C11 requirement. We see it causes pain to many, and we feel that the value (in code clarity) is not worth the pain, and that it was too early for Redis to depend on it. We'll reconsider it again in the future. This ticket is closed, and the task will be tracked in #7509.