RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Good day.
Following darktable build fails on ppc64le only. In past a similar problem was caused by a bug in OpenMP / GCC, so I wanted to report this problem here.

epel8-next https://koji.fedoraproject.org/koji/taskinfo?taskID=85563318
epel8 https://koji.fedoraproject.org/koji/taskinfo?taskID=85568505

the compiler seems to fail on file darktable/src/common/fast_guided_filter.h
Best regards

So this looks like a dup of https://bugzilla.redhat.com/show_bug.cgi?id=2038839

What is different this time?  What gcc is used to build darktable?

gcc-toolset-11 has been now used. Instead in 
https://bugzilla.redhat.com/show_bug.cgi?id=2038839
it was GCC 8.5

I see.  Argh, I thought this worked: https://bugzilla.redhat.com/show_bug.cgi?id=2038839#c1
So no clue why it doesn't work now.  Will have to try to reproduce...

If you need any help, let me know

In devel.org I have been told that a similar problem is being solved in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059

Seems the darktable build isn't using gcc 11 from the toolset, but the system one (8.5). The toolset's gcc isn't enabled correctly, a PR will follow.

Hello, this bugreport can be closed as "not a bug" since I did not correctly enable GCC toolset 11, but this has now been fixed by Dan Horák in
https://src.fedoraproject.org/rpms/darktable/pull-request/6
and
https://src.fedoraproject.org/rpms/darktable/pull-request/7

and the package is correctly building
https://koji.fedoraproject.org/koji/buildinfo?buildID=1948510

Cheers

(In reply to Germano Massullo from comment #7)
> Hello, this bugreport can be closed as "not a bug" since I did not correctly
> enable GCC toolset 11, but this has now been fixed by Dan Horák in
> https://src.fedoraproject.org/rpms/darktable/pull-request/6
> and
> https://src.fedoraproject.org/rpms/darktable/pull-request/7
> 
> and the package is correctly building
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1948510
> 
> Cheers

Great.

Closing then.