GLIBC 2.26 building error

[gdf]

Hello hackers!

I am updating glibc on centos7,I have made gcc newest to be gcc-12.2.0.

while making glibc2.26, I met following error:
../sysdeps/nptl/pthread.h:744:47: error: argument 1 of type ‘struct __jmp_buf_tag *’ declared as a pointer [-Werror=array-parameter=]
744 | extern int __sigsetjmp (struct __jmp_buf_tag *__env, int __savemask) __THROWNL;
|

~~~~~~~~~~~~~~~~~~~^~~~~
In file included from ../include/setjmp.h:2,
                 from ../nptl/descr.h:24:
../setjmp/setjmp.h:54:46: note: previously declared as an array ‘struct __jmp_buf_tag[1]’
   54 | extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask) __THROWNL;
      |                         ~~~~~~~~~~~~~~~~~~~~~^~~~~

In file included from ../include/pthread.h:1,
from ../nptl/../nptl_db/thread_db.h:25,
from ../nptl/descr.h:32,
from ../sysdeps/x86_64/nptl/tls.h:113,
from ../sysdeps/unix/sysv/linux/x86_64/sysdep.h:24,
from <stdin>:2:
../sysdeps/nptl/pthread.h:744:47: error: argument 1 of type ‘struct __jmp_buf_tag *’ declared as a pointer [-Werror=array-parameter=]
744 | extern int __sigsetjmp (struct __jmp_buf_tag *__env, int __savemask) __THROWNL;
|

~~~~~~~~~~~~~~~~~~~^~~~~
In file included from ../include/setjmp.h:2,

[B][SIZE=5]from ../nptl/descr.h:24:[/SIZE][/B]
[SIZE=5][B]../setjmp/setjmp.h:54:46: note: previously declared as an array ‘struct __jmp_buf_tag[1]’
   54 | extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask) __THROWNL;[/B][/SIZE]
      |                         ~~~~~~~~~~~~~~~~~~~~~^~~~~

cc1: all warnings being treated as errors
cc1: all warnings being treated as errors


How can I fix this problem?
OS-kernel: 3.10.0-862.el7.x86_64
CentOS Linux release 7.5.1804 (Core)

Best wishes for all of you!

 

[f33dm3bits]

I don't compile source code very often so it's not my strong suit. What did you run to compile glibc from source and where did you install gcc 12 from, from software collections(devtoolset 12) I would think?

 

[osprey]

gdf wrote:

cc1: all warnings being treated as errors

What happens if you turn off treating all warnings as errors?