Re: pthread in glibc2.2.2

[Dan Maas]

> > Glibc 2.2.2 and linuxthreads *compiled with LDT enabled* cause any
program
> > that is linked to libpthread.so to SEGV immediately on startup.
>
> That's not true.  The problem is that you are using outdated binutils
> or something like that which causes libpthread to not be built with
> DF_1_INITFIRST set.

Maintainers, let's stop this from happening again. There is a version check
for binutils in configure.in, except it's been commented out ("filters out
too many good versions"). I highly recommend un-commenting this check. There
have been FOUR spurious bug reports to bug-glibc due to this silent failure,
and ZERO from people with old (but functional) binutils. Patch below.

I confirm that Ulrich is correct. Upgrading binutils from 2.9.1 to 2.10.1
fixes 99% of all threaded programs. (Mozilla still gives the same SEGV, but
I assume it's already playing some dirty games with the linker so I'm not
terribly worried...)

Regards,
Dan

--- configure.in        Fri Feb  9 13:36:07 2001
+++ configure.in-new    Mon Apr  2 16:25:32 2001
@@ -579,11 +579,9 @@
 AC_CHECK_TOOL(MIG, mig)

 # Accept binutils 2.10.1 or newer (and also any ia64 2.9 version)
-# XXX Commented out because it filters out too many good versions.
-# XXX --drepper
-# AC_CHECK_PROG_VER(AS, $AS, --version,
-#   [GNU assembler.* \([0-9]*\.[0-9.]*\(-ia64-[0-9]*\)*\)],
-#   [2.10.[1-9]* | 2.1[1-9]* | 2.9-ia64-*], AS=: critic_missing=t)
+AC_CHECK_PROG_VER(AS, $AS, --version,
+  [GNU assembler.* \([0-9]*\.[0-9.]*\(-ia64-[0-9]*\)*\)],
+  [2.10.[1-9]* | 2.1[1-9]* | 2.9-ia64-*], AS=: critic_missing=t)

 if test -n "$critic_missing"; then
 AC_MSG_ERROR([