On Tue, 24 Jan 2023 at 07:11, Josh Boyer <jwboyer@xxxxxxxxxx> wrote:
On Tue, Jan 24, 2023 at 7:01 AM Sérgio Basto <sergio@xxxxxxxxxx> wrote:
>
> Hi,
> Sorry, now subject is correct, the gcc have one patch for the error
> above, that is seen on rhel 9
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1996330#c14
If you believe this is present in RHEL 9, please clone the bug to the
Red Hat Enterprise Linux 9 bugzilla family.
Also going from someone I pinged:
Please check if it is a duplicate of either bug first:
gcc: Incorrect always_inline diagnostic in LTO mode with #pragma GCC
target("cpu=power10")
<https://bugzilla.redhat.com/show_bug.cgi?id=2140266>
digikam builds fail with gcc 11.3.1-4 (target specific option mismatch)
<https://bugzilla.redhat.com/show_bug.cgi?id=2159428>
gcc: Incorrect always_inline diagnostic in LTO mode with #pragma GCC
target("cpu=power10")
<https://bugzilla.redhat.com/show_bug.cgi?id=2140266>
digikam builds fail with gcc 11.3.1-4 (target specific option mismatch)
<https://bugzilla.redhat.com/show_bug.cgi?id=2159428>
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue