public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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: Mon, 2 May 2022 20:02:07 +1000	[thread overview]
Message-ID: <CAEYL+X9GO7u47oTiCTujiDmwS0dQe+cWxeavFg986wfhEdom9A@mail.gmail.com> (raw)
In-Reply-To: <aad10798fdbb66b79cdcf8136b5c71c659954c27.camel@mengyan1223.wang>

The thing is, that builds fine, but I havent changed anything to do
with libstdc++-v3.

On Mon, May 2, 2022 at 7:29 PM Xi Ruoyao <xry111@mengyan1223.wang> wrote:

> On Mon, 2022-05-02 at 19:20 +1000, Zopolis0 via Gcc-help wrote:
> > While trying to compile gcj, it breaks on a number of errors, many of
> which
> > are along the lines of "no matching function for call to ‘operator
> > new(sizetype, sizetype)". However, I have not touched this code, and this
> > error does not appear on another branch which is a few months back from
> > master. This leads me to believe that this is an error present on master,
> > although I have not yet been able to locate the breaking commit. (Example
> > of one such error:)
>
> Don't guess.  Just build the unmodified trunk and if it fails reports to
> https://gcc.gnu.org/bugzilla.
> --
> Xi Ruoyao <xry111@mengyan1223.wang>
> School of Aerospace Science and Technology, Xidian University
>

  reply	other threads:[~2022-05-02 10:02 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 [this message]
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

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+X9GO7u47oTiCTujiDmwS0dQe+cWxeavFg986wfhEdom9A@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).