So I updated to base 3-1 (from 2-2) which includes glibc 2.36 and for whatever reason, ldd output on virtually every file changed. For example, running ldd /bin/bash:
glibc 2.35 (output from my friend running Archlinux)
linux-vdso.so.1 (0x00007ffeed5b3000)
libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f0be5381000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f0be537c000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f0be5000000)
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f0be5308000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f0be54f4000)
glibc 2.36:
linux-vdso.so.1 => linux-vdso.so.1 (0x00007ffe37744000)
libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f84a3038000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f84a3033000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f84a2e4f000)
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f84a2ddb000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f84a31ae000)
linux-vdso.so.1 now points to itself, which can break compilers. In particular it breaks Nuitka (which worked before the update), and I’d imagine there are others too. I have no idea if its a bug or a feature, and no idea whether this is a bug on my local machine but yeah it is a breaking change if it is a change.
the autogenerated log: https://clbin.com/drJI1
