From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8599E3858C52; Sat, 30 Dec 2023 12:02:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8599E3858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1703937742; bh=zGPPXnS4r6J/ij3tfKuSNvwttrddLIRoQmt33sFjCtQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pIUOb77kK6fFkFSBgHpO4sOyyOPRytNuVqzGUFAiWeko/OYU4FwRflp4rL3M6Q2gv YilSZpQo3o/4BV3nrSSA7c7rtdvw3xUxQg1Kn6XWXhw50arLh0WqDgZAYLao8o8dI2 YGJml22T64N0LLyg0ISFUsk1FC/Dc/HU40wDa5p8= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++ Date: Sat, 30 Dec 2023 12:02:20 +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: unknown X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: NEW 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: bug_status cc everconfirmed cf_reconfirmed_on 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=3D87858 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |xry111 at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2023-12-30 --- Comment #14 from Xi Ruoyao --- Confirm as this has been asked via gcc-help multiple times. A possible work around is to install the static libstdc++ (libstdc++.a) provided by the distro. But this is not documented anywhere and it's still just a work around, not a fix. Note that patches should be sent to gcc-patches@gcc.gnu.org instead of (or = in addition to) posting here. The patches in bugzilla generally do not get any review seriously.=