public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/13411] New: glibc fails to build with gcc 4.7
@ 2011-11-15 15:22 matz at suse dot de
  2011-11-15 15:49 ` [Bug libc/13411] " matz at suse dot de
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: matz at suse dot de @ 2011-11-15 15:22 UTC (permalink / raw)
  To: glibc-bugs

http://sourceware.org/bugzilla/show_bug.cgi?id=13411

             Bug #: 13411
           Summary: glibc fails to build with gcc 4.7
           Product: glibc
           Version: 2.14
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: matz@suse.de
    Classification: Unclassified


This is also http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51117 .
gcc can emit calls to _Unwind_Resume for files compiled with -fexceptions,
new GCCs do this more often than earlier.  This currently leads to a linking
failure due to symbols defined twice:

cc   -nostdlib -nostartfiles -r -o /var/tmp/glibc-build/libc_pic.os \
 -Wl,-d -Wl,--whole-archive /var/tmp/glibc-build/libc_pic.a -o
/var/tmp/glibc-build/libc_pic.os
gcc   -nostdlib -nostartfiles -r -o /var/tmp/glibc-build/elf/librtld.map.o
'-Wl,-(' /var/tmp/glibc-build/elf/dl-allobjs.os /var/tmp/glibc-build/libc_
pic.a -lgcc '-Wl,-)' -Wl,-Map,/var/tmp/glibc-build/elf/librtld.mapT
/var/tmp/glibc-build/libc_pic.a(dl-addr.os): In function
`_dl_addr_inside_object':
/var/tmp/glibc/elf/dl-addr.c:155: multiple definition of
`_dl_addr_inside_object'
/var/tmp/glibc-build/elf/dl-allobjs.os:/var/tmp/glibc/elf/dl-open.c:673: first
defined here

The problem is that dl-addr.so is included in the link, due to this
symbol requirement chain:

dl-allobjs.os (_Unwind_Resume)
unwind-resume.os (__GI___libc_fatal)
libc_fatal.os (__GI___backtrace_symbols_fd)
backtracesymfd.os (__GI__dl_addr)
dl-addr.os

Somehow this chains needs to be broken by either providing one of these
symbols from dl-allobjs.os already, or by not compiling the respective files
with -fexceptions.

I'm not sure why they are compiled with -fexceptions,
-fasynchronous-unwind-tables ought to be enough to make
unwinding through these routines work (it's related to cancellation points,
right?)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 10+ messages in thread
end of thread, other threads:[~2014-06-27 11:35 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-15 15:22 [Bug libc/13411] New: glibc fails to build with gcc 4.7 matz at suse dot de
2011-11-15 15:49 ` [Bug libc/13411] " matz at suse dot de
2011-11-15 16:07 ` cryptooctoploid at gmail dot com
2011-11-16 11:51 ` ibolton at gcc dot gnu.org
2011-11-16 19:10 ` hjl.tools at gmail dot com
2011-11-17  8:41 ` schwab@linux-m68k.org
2011-11-17 15:15 ` matz at suse dot de
2011-12-07 21:58 ` mpolacek at redhat dot com
2011-12-14 10:49 ` cryptooctoploid at gmail dot com
2014-06-27 11:35 ` fweimer at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).