public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/26260] undefined reference to `_Unwind_Resume' Date: Fri, 17 Jul 2020 20:48:35 +0000 [thread overview] Message-ID: <bug-26260-131-csT3p61yLg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26260-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26260 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Linking libc with libgcc_eh is not correct. See the four-paragraph comment on the definitions of libunwind, gnulib and related variables for an explanation. There are various requirements on libgcc and the GCC build process to avoid such circular dependencies and to ensure that a stripped glibc binary built with an inhibit_libc GCC is identical to one built following a longer sequence of alternating GCC and glibc builds. It seems you've found another such requirement: libgcc must not be built in a way that introduces references to EH symbols in the code statically linked into shared libc. glibc does not itself support being built with -O0 either. It would be desirable to do so, but there might still be requirements in that case for some individual files or functions to be compiled with optimization. Likewise, even if a libgcc mostly built with -O0 works for building glibc, it seems optimization might be required for building some files therein. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2020-07-17 20:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-17 20:07 [Bug build/26260] New: " sourceware@le-garrec.fr 2020-07-17 20:08 ` [Bug build/26260] " sourceware@le-garrec.fr 2020-07-17 20:48 ` joseph at codesourcery dot com [this message]
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-csT3p61yLg@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: linkBe 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).