public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sourceware@le-garrec.fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26260] New: undefined reference to `_Unwind_Resume'
Date: Fri, 17 Jul 2020 20:07:55 +0000	[thread overview]
Message-ID: <bug-26260-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26260
           Summary: undefined reference to `_Unwind_Resume'
           Product: glibc
           Version: 2.31
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: sourceware@le-garrec.fr
                CC: carlos at redhat dot com
  Target Milestone: ---

I can't build glibc if gcc was built with -O0 option. I open a bug in the GCC
project (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96217) but they told me
the problem was in glibc.

The glibc log says :

/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/../../../../x86_64-pc-linux-gnu/bin/ld.bfd:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/32/libgcc.a(_divdi3.o): in function
`__divdi3':
/var/tmp/portage/sys-devel/gcc-10.1.0-r2/work/gcc-10.1.0/libgcc/libgcc2.c:1246:
undefined reference to `_Unwind_Resume'
/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/../../../../x86_64-pc-linux-gnu/bin/ld.bfd:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/32/libgcc.a(_divdi3.o):(.data.rel.local.DW.ref.__gcc_personality_v0[DW.ref.__gcc_personality_v0]+0x0):
undefined reference to `__gcc_personality_v0'
/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/../../../../x86_64-pc-linux-gnu/bin/ld.bfd:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.1.0/32/libgcc.a(_moddi3.o): in function
`__moddi3':
/var/tmp/portage/sys-devel/gcc-10.1.0-r2/work/gcc-10.1.0/libgcc/libgcc2.c:1269:
undefined reference to `_Unwind_Resume'

The solution is to make a change in Makeconfig :
from
gnulib = -lgcc $(gnulib-arch)
to
gnulib = -lgcc -lgcc_eh $(gnulib-arch)

What do you think of this change ? Do you think that glibc should supports -O0
compilation ?

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

             reply	other threads:[~2020-07-17 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 20:07 sourceware@le-garrec.fr [this message]
2020-07-17 20:08 ` [Bug build/26260] " sourceware@le-garrec.fr
2020-07-17 20:48 ` joseph at codesourcery dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-26260-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).