From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Fri, 13 Nov 2020 10:23:08 +0000 (+0000)
Subject: hurd: Make sure signals get started
X-Git-Tag: glibc-2.33~304
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0f73c170379a34363c95e6ceab7b30bd4fe66c25;p=thirdparty%2Fglibc.git

hurd: Make sure signals get started

Now that _hurd_libc_proc_init is idempotent, we can always call it,
independently of the __libc_multiple_libcs test which may not match
whether signals should be started or not.
---

diff --git a/sysdeps/mach/hurd/i386/init-first.c b/sysdeps/mach/hurd/i386/init-first.c
index a3d2fdaba03..1827479f86f 100644
--- a/sysdeps/mach/hurd/i386/init-first.c
+++ b/sysdeps/mach/hurd/i386/init-first.c
@@ -58,14 +58,14 @@ posixland_init (int argc, char **argv, char **envp)
 {
   __libc_multiple_libcs = &_dl_starting_up && !_dl_starting_up;
 
+  /* Now we have relocations etc. we can start signals etc.  */
+  _hurd_libc_proc_init (argv);
+
   /* Make sure we don't initialize twice.  */
   if (!__libc_multiple_libcs)
     {
       /* Set the FPU control word to the proper default value.  */
       __setfpucw (__fpu_control);
-
-      /* Now we have relocations etc. we can start signals etc.  */
-      _hurd_libc_proc_init (argv);
     }
   else
     {