Update on the glibc segfault issue on Alpha

Hello!

Just a quick update on the glibc issue we're seeing on Alpha!

My previous bisecting result was wrong and the segfault I ran into was the result
of combining ld.so and libc.so files from different builds by not including all
necessary paths in my LD_LIBRARY_PATH. So, my previously reported bug report was
invalid [1].

However, as can be seen from the build logs, there are still clearly issues with
the testsuite [2]. Further analysis showed that the problem are static binaries
which segfault. Anything dynamically linked, works.

This becomes obvious when building the glibc Debian package manually with the testsuite
disabled and then installing these packages inside a test chroot. While the libc-bin
package is being configured, ldconfig is run - a statically linked binary - and crashes
with a segfault.

Adhemerval from glibc upstream is aware of the problem but he has not found yet a solution
to this issue as it needs to be debugged further. I will try to bisect which particular
introduced the regression and file a new upstream bug report.

During our discussion, Adhemerval pointed out that this change [3] might be the culprit
but I have not been able to verify this yet.

Adrian

> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=29899
> [2] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=alpha&ver=2.36-6&stamp=1669706903&raw=0
> [3] https://sourceware.org/pipermail/glibc-cvs/2020q2/069444.html