On Mon, 2022-05-02 at 20:02 +1000, Zopolis0 wrote: > The thing is, that builds fine, but I havent changed anything to do > with libstdc++-v3. Then maybe you've modified some compiler code common for languages and cause GCC to misbehave on libstdc++ code (then stage 1 libstdc++ fails), or maybe it causes GCC to miscompile itself and generate a compiler misbehaving on libstdc++ code (so stage 2 libstdc++ fails). Or maybe some modification to the building system causes libstdc++ built with wrong CXXFLAGS. Who knows? We have no idea how the code is modified. > On Mon, May 2, 2022 at 7:29 PM Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx> > 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@xxxxxxxxxxxxxxxx> School of Aerospace Science and Technology, Xidian University
