[Bug libc/21936] New: gcc build hangs with glibc 2.26 (conftest about static binaries dlopening themselves)

["felix-glibc at fefe dot de" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=21936

            Bug ID: 21936
           Summary: gcc build hangs with glibc 2.26 (conftest about static
                    binaries dlopening themselves)
           Product: glibc
           Version: 2.26
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: felix-glibc at fefe dot de
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

I recently upgraded to glibc 2.26. I have had this issue for a long while, but
it went away with glibc 2.25 or so I thought. Now it's back.

Basically, when I try to compile gcc from the sources, in multiple
subdirectories there are autoconf tests that are trying to find out whether a
statically linked binary can dlopen itself. The conftest from those tests
hangs.

I looked through previous bugs, and they make a mention of gold from binutils.
I am using gcc 7.1 and binutils 2.29 (and I was trying to compile the current
gcc from svn). ld is:

GNU ld (GNU Binutils) 2.29

(not gold).

This problem basically breaks unattended builds and is VERY annoying for that
reason. I'm not even sure why gcc would want to know if static binaries can
dlopen themselves.

-- 
You are receiving this mail because:
You are on the CC list for the bug.