While trying to build glibc-2.30 with gcc-10.2.0 an error occured:
-----------------------
libc-tls.c: In function '__libc_setup_tls':
libc-tls.c:209:30: error: array subscript 1 is outside the bounds of an interior zero-length array 'struct dtv_slotinfo[0]' [-Werror=zero-length-bounds]
209 | static_slotinfo.si.slotinfo[1].map = main_map;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
In file included from ../sysdeps/x86/ldsodefs.h:64,
from ../sysdeps/gnu/ldsodefs.h:46,
from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
from libc-tls.c:21:
../sysdeps/generic/ldsodefs.h:406:7: note: while referencing 'slotinfo'
406 | } slotinfo[0];
-----------------------

And according to this message, glibc-2.30 has non backported patch to build with gcc-10.2.0 : https://gcc.gnu.org/legacy-ml/gcc-pa.../msg00449.html

As I reported this morning in the 14.2->15.0 thread, glibc-2.32 does build without problems using gcc-10.2.0. So, either the 2.30 code needs to be patched or -current needs to jump to 2.32.

1 members found this post helpful.

Finally got glibc-2.30 built with gcc-10.2.0, follow link for the details:
https://github.com/nobodino/slackwar...urrent/l/glibc

1 members found this post helpful.

Thanks. I needed this for ARM and AArch64.
Happy new year! :-)

Thank you nobodino. glibc built fine now with 10.2.0

It turns out that this patch breaks the build on ARM and isn't required because --disable-werror is a default configuration option on SlackARM. glibc should build on x86/64 without patching when you use this option.

I was looking at this happening a few days ago, and skipped patching, since I could just use Pat's glibc anyway. This is one of those things that makes recompiling things reproducibly (or a slackware from scratch) pretty much a chore. The way to get to what Pat has would be to go through the steps of old gcc > glibc 2.30 -> new gcc. If you patch glibc to make it compile, now you are compiling a different (how much?) glibc than what is in slackware.

What drmozes says of using --disable-werror actually brings you closer to the actual glibc built, as long as gcc 9.3.0 and gcc 10.2.0 didn't really diverge in code generation. If you want to be like LFS and teach/show people what slackware is like, I would actually just put the ignore in rather than patch things to compile on things like this. And I think the project makes more sense to me to base on a stable series of Slackware. But I know you only recently got started during this -current.

Also, I was looking at the bug report for glibc concerning gcc 10.2 and it looked like some patches were applied, and more were needed later for other platforms. So how would one handle multiple platforms, in a source based distro, on a platform that slackware was not initially tested on?

the -current slackware git tree has been updated to allow glibc-2.30 to build with gcc-10.2.0 follow link: https://git.slackware.nl/current/dif...518ca5fffdc694