title: Error concerning an " undefined reference to `__dso_handle' " when complinging Glibc
body: <p>I am working on a Linux from Scratch system for the first time.</p>
  <p>Background Info:</p>
  <p>Book version - 10.1</p>
  <p>Host distrobution - EndeavorOS</p>
  <p>Problem occurs in step 5.5.1 <a href="https://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html" rel="nofollow noreferrer">https://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html</a></p>
  <p>I begin to compile Glibc, but then about a minute or so in it ends the process. It appears things start to go downhill here:</p>
  <pre><code>/mnt/lfs/tools/lib/gcc/x86_64-lfs-linux-gnu/10.2.0/../../../../x86_64-lfs-lin
  ux-gnu/bin/ld: /mnt/lfs/sources/glibc-2.33/build/nptl/libpthread_pic.a(old_pt
  hread_atfork.os): in function `__dyn_pthread_atfork':
  /mnt/lfs/sources/glibc-2.33/nptl/pthread_atfork.c:51: undefined reference to
  `__dso_handle'
  /mnt/lfs/tools/lib/gcc/x86_64-lfs-linux-gnu/10.2.0/../../../../x86_64-lfs-lin
  ux-gnu/bin/ld: /mnt/lfs/sources/glibc-2.33/build/nptl/libpthread_pic.a(old_pt
  hread_atfork.os): relocation R_X86_64_PC32 against undefined hidden symbol `_
  _dso_handle' can not be used when making a shared object
  /mnt/lfs/tools/lib/gcc/x86_64-lfs-linux-gnu/10.2.0/../../../../x86_64-lfs-lin
  ux-gnu/bin/ld: final link failed: bad value
  collect2: error: ld returned 1 exit status
  make[2]: *** [../Makerules:536: /mnt/lfs/sources/glibc-2.33/build/nptl/libpth
  read.so] Error 1
  make[2]: Leaving directory '/mnt/lfs/sources/glibc-2.33/nptl'
  make[1]: *** [Makefile:479: nptl/others] Error 2
  make[1]: Leaving directory '/mnt/lfs/sources/glibc-2.33'
  make: *** [Makefile:9: all] Error 2
  [lfs@Endeavour build]$
  </code></pre>
  <p>(The full non-shortened output can be found here: <a href="https://pastebin.com/7Qk40xr2" rel="nofollow noreferrer">https://pastebin.com/7Qk40xr2</a>)</p>
  <p>Multiple times it mentions `__dso_handle'</p>
  <p>I have tried using &quot;make -j4&quot;, &quot;make&quot;, and &quot;make -j1&quot;, but they all lead to the same problem.</p>
  <p>If any assistance could be provided, I would be grateful.</p>