From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mengyan1223.wang (mengyan1223.wang [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 60FE13858C50 for ; Mon, 2 May 2022 12:42:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 60FE13858C50 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@mengyan1223.wang) by mengyan1223.wang (Postfix) with ESMTPSA id F39C666577; Mon, 2 May 2022 08:42:39 -0400 (EDT) Message-ID: <17837bee5618c45e63b2a1e47faf34f87e83552b.camel@mengyan1223.wang> Subject: Re: libstdc++-v3 failing to compile due to no matching function for call to =?gb2312?Q?=A1=AEoperator?= new(sizetype, sizetype) From: Xi Ruoyao To: Zopolis0 Cc: gcc-help@gcc.gnu.org Date: Mon, 02 May 2022 20:42:37 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.1 MIME-Version: 1.0 X-Spam-Status: No, score=-3028.6 required=5.0 tests=BAYES_00, CHARSET_FARAWAY_HEADER, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2022 12:42:43 -0000 On Mon, 2022-05-02 at 22:07 +1000, Zopolis0 wrote: > I've bisected the issue (which still happens with only --enable- > languages=3Dc,c++ instead of --enable-languages=3Djava), > and=C2=A00a0c2c3f06227d46b5e9542dfdd4e0fd2d67d894 is the first bad commit > apparently. I think I've done it wrong though, and > that=C2=A07a42b1fa1a090ead96cc0f94a8060a9650c810d5 is the breaking change= . Again, don't guess. You can revert one of those changes or both of them to try. As I've indicated, you can't just look the diagnostic output from the compiler and guess "this is the relevant modification, that is not". You are compiling libstdc++ with g++, so a change to either libstdc++ or g++ may break the compiliation. --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University