From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 36474387085F; Fri, 17 Jul 2020 20:48:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 36474387085F From: "joseph at codesourcery dot com" To: glibc-bugs@sourceware.org Subject: [Bug build/26260] undefined reference to `_Unwind_Resume' Date: Fri, 17 Jul 2020 20:48:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: build X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2020 20:48:35 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26260 --- Comment #1 from joseph at codesourcery dot com --- Linking libc with libgcc_eh is not correct. See the four-paragraph=20 comment on the definitions of libunwind, gnulib and related variables for=20 an explanation. There are various requirements on libgcc and the GCC=20 build process to avoid such circular dependencies and to ensure that a=20 stripped glibc binary built with an inhibit_libc GCC is identical to one=20 built following a longer sequence of alternating GCC and glibc builds.=20=20 It seems you've found another such requirement: libgcc must not be built=20 in a way that introduces references to EH symbols in the code statically=20 linked into shared libc. glibc does not itself support being built with -O0 either. It would be=20 desirable to do so, but there might still be requirements in that case for= =20 some individual files or functions to be compiled with optimization.=20=20 Likewise, even if a libgcc mostly built with -O0 works for building glibc,= =20 it seems optimization might be required for building some files therein. --=20 You are receiving this mail because: You are on the CC list for the bug.=