public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at logicalclocks dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104244] Crash compiling RonDB 22.01 on Oracle Linux 8 on ARM
Date: Wed, 26 Jan 2022 22:43:54 +0000	[thread overview]
Message-ID: <bug-104244-4-wQAVImh00S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104244-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104244

--- Comment #6 from mikael at logicalclocks dot com ---
Hi,
Gather I could send the same bug info to Oracle as well.
Regarding the -save-temps to the failing command it is
a bit difficult since I simply run make which has its
make files created by CMake. I gather there is some method
to find out how to generate the actual commands, but it is
deeply hidden from normal developers these days, was easier
in the past.

  parent reply	other threads:[~2022-01-26 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 15:39 [Bug c++/104244] New: " mikael at logicalclocks dot com
2022-01-26 18:49 ` [Bug c++/104244] " pinskia at gcc dot gnu.org
2022-01-26 18:50 ` pinskia at gcc dot gnu.org
2022-01-26 22:34 ` mikael at logicalclocks dot com
2022-01-26 22:38 ` pinskia at gcc dot gnu.org
2022-01-26 22:39 ` pinskia at gcc dot gnu.org
2022-01-26 22:43 ` mikael at logicalclocks dot com [this message]
2022-01-26 22:52 ` mikael at logicalclocks dot com
2024-04-13  1:11 ` 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-104244-4-wQAVImh00S@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: 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).