From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4D8E83858C62; Mon, 24 Apr 2023 19:55:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D8E83858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682366153; bh=mimYHb+goGWSTAV8jQ371E1wwTHHgdpGwyx+t6ArEBs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=L2pgXSnbLYzoMg5aaHS8flIHg2TE4rVuooYt9pLiK78fD6jht5bcIz8NZhQDn//08 XcGNqydZDhKdO+01ziTJvvYeQB66uzKVn7eAQj8jenEjWJfEcfHeOyJxEI3zEq3kbV X1b1C/WJL0qNucIvcNVJRePQfhKPUI/2gV2gXWB0= From: "arsen at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/105688] GCC 11.3 doesn't build with the GNU gold linker (version 2.37-27.fc36) 1.16: libstdc++.so.6: version `GLIBCXX_3.4.30' not found Date: Mon, 24 Apr 2023 19:55:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 11.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arsen at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105688 Arsen Arsenovi=C4=87 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arsen at gcc dot gnu.org --- Comment #45 from Arsen Arsenovi=C4=87 --- to recap what I've found in the bug that just got marked as a dupe: this is set through a chain of all-target-libstdc++-v3 -> RAW_CXX_TARGET_EXPORTS -> BASE_TARGET_EXPORTS the idea here is that newly-built target code should use existing target libraries rather than $build libraries (which makes sense). however, the existing approach makes *all* code involved in building target libs use newly-built libraries, which results in libstdc++ et al being *downgraded* for make, sh, msgfmt, ld, ... (but not gcc, since the new gcc = is used). a fix for this might be to build target libraries with adjusted rpaths, or something similar, but I'm not sure of the full scope of the issue yet (my debugging this morning was cursory), so I'm not sure if that's sufficient. = I'm also not sure how to deal with static linking - maybe libtool helps?=