From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Xi Ruoyao <xry111@mengyan1223.wang>
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc++-v3 failing to compile due to no matching function for call to ‘operator new(sizetype, sizetype)
Date: Tue, 3 May 2022 15:30:21 +1000 [thread overview]
Message-ID: <CAEYL+X_U94fzn8a3oecjxr250h7FyR0FDPWXX6-s+osJDp3GNg@mail.gmail.com> (raw)
In-Reply-To: <17837bee5618c45e63b2a1e47faf34f87e83552b.camel@mengyan1223.wang>
Turns out it was some code from 0a0c2c3f06227d46b5e9542dfdd4e0fd2d67d894 I
acidentally deleted in a rebase, fixed.
On Mon, May 2, 2022 at 10:42 PM Xi Ruoyao <xry111@mengyan1223.wang> wrote:
> On Mon, 2022-05-02 at 22:07 +1000, Zopolis0 wrote:
> > I've bisected the issue (which still happens with only --enable-
> > languages=c,c++ instead of --enable-languages=java),
> > and 0a0c2c3f06227d46b5e9542dfdd4e0fd2d67d894 is the first bad commit
> > apparently. I think I've done it wrong though, and
> > that 7a42b1fa1a090ead96cc0f94a8060a9650c810d5 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.
> --
> Xi Ruoyao <xry111@mengyan1223.wang>
> School of Aerospace Science and Technology, Xidian University
>
prev parent reply other threads:[~2022-05-03 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:20 Zopolis0
2022-05-02 9:29 ` Xi Ruoyao
2022-05-02 10:02 ` Zopolis0
2022-05-02 10:24 ` Xi Ruoyao
2022-05-02 12:07 ` Zopolis0
2022-05-02 12:42 ` Xi Ruoyao
2022-05-03 5:30 ` Zopolis0 [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=CAEYL+X_U94fzn8a3oecjxr250h7FyR0FDPWXX6-s+osJDp3GNg@mail.gmail.com \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@mengyan1223.wang \
/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: link
Be 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).