public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "estellnb at elstel dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105293] g++-8/i586: internal compiler error trying to compile with g++ (evtl. related to qt5/moc bug) Date: Sun, 17 Apr 2022 15:13:21 +0000 [thread overview] Message-ID: <bug-105293-4-ntGmaqqj8L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105293-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105293 --- Comment #3 from Elmar Stellnberger <estellnb at elstel dot org> --- Created attachment 52823 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52823&action=edit patch that should be useable under gcc-8-8.3.0/debian/patches/ I have recompiled g++ and the output of dpkg-buildpackage -b -kestellnb@elstel.org -nc tells me that it should have successfully created the respective .deb package files as before. I have looked into the same directory as before but unfortunately I found not a single .deb there and nowhere else under /usr/src. The files can only have been deleted like the ssh user from /etc/passwd at my nslu2 machine. Another time I found out about a chmod -x /etc/init.d/sshd as I suddenly could not connect to my nslu2 via ssh any more. This looks very similar as what I have experienced with arm-linux-gnueabihf-ld when the program did neither produce an error message, an !=0 return value and no output file as given with -o txtfmt. This was when I had all options right to what I can assess, i.e. just before it must have worked. As for now I can not find out whether the patch really resolves the bug. Someone else will have to be as nice to recompile for me. The patch makes a forward change to a known good g++ (version as suggested by use of moc/Qt5 rather than by building Firefox however). It patches the only piece of code that was different along the backtrace of Firefox-esr-91.8.0esr.
next prev parent reply other threads:[~2022-04-17 15:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 18:31 [Bug c++/105293] New: " estellnb at elstel dot org 2022-04-16 18:56 ` [Bug c++/105293] " estellnb at elstel dot org 2022-04-17 9:35 ` estellnb at elstel dot org 2022-04-17 15:13 ` estellnb at elstel dot org [this message] 2022-04-17 18:31 ` estellnb at elstel dot org 2022-04-18 17:38 ` estellnb at elstel dot org 2022-04-19 9:25 ` rguenth at gcc dot gnu.org 2024-04-13 1:17 ` pinskia at gcc dot gnu.org
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=bug-105293-4-ntGmaqqj8L@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).