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:34:03 +0000	[thread overview]
Message-ID: <bug-104244-4-D9bVgz3BRA@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 #3 from mikael at logicalclocks dot com ---
Sorry, I am not an expert in GCC lingo, so plugin in the context
of GCC I don't know what it means. MySQL have lots of plugins, but
I assume this is not what you refer to.

Unfortunately I didn't gather the preprocessed source and don't
really know how to do it either. I gathered as much as I could.

But the problem is very repeatable, so should not be very difficult
to reproduce.

I used a VM in OCI with Oracle Linux 8.5 Cloud Developer version
where I installed as directed by CMake.

It does work with GCC 10.2.1 on the same OS I can mention although
I failed in downgrading, but I had it working on a different VM
which is a bit older and still had 10.2.1 installed.

Tried compiling on Ubuntu using 20.04 in OCI which is some version
of 10.3.0. This didn't fail in the same manner, instead it failed
in a missing symbol dlopen in 2.17 (presume it is GLIBC it refers to).

  parent reply	other threads:[~2022-01-26 22:34 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 [this message]
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
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-D9bVgz3BRA@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).