Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
digikam is still failing with 11.3.1-4:
/usr/include/eigen3/Eigen/src/Core/util/BlasUtil.h:227:46: error: inlining failed in call to 'always_inline' 'Eigen::internal::blas_data_mapper<double, long, 0, 0, 1>::storePacketBlock<double __vector(2), 4>(long, long, Eigen::internal::PacketBlock<double __vector(2), 4> const&) constvoid': target specific option mismatch
See https://koji.fedoraproject.org/koji/taskinfo?taskID=95750885
Found and pointed out by Orion Poplawski in bz2140266#c8.
Version-Release number of selected component (if applicable):
gcc-11.3.1-4.el9
Additional info:
bz2140266 but its fix seems not to help with digikam
(In reply to Václav Kadlčík from comment #0)
...
> bz2140266 but its fix seems not to help with digikam
should have been "bz2140266 seems related but ..."
Reproduced without Koji and without mock on a RHEL 9.2 build
with gcc-11.3.1-4.3.el9.ppc64le:
1. Install/enable the CodeReady (CRB) and EPEL repositories
2. Install packages according to attached rpms.txt
3. Prepare the sources:
mkdir -p rpmbuild/SPECS rpmbuild/SOURCES
wget -O rpmbuild/SPECS/digikam.spec \
https://src.fedoraproject.org/rpms/digikam/raw/59a551c6c1b4a104452a8ab4124cca5c6444cd57/f/digikam.spec
wget -O rpmbuild/SOURCES/digiKam-7.9.0.tar.xz \
https://ftp.fi.muni.cz/pub/kde/stable/digikam/7.9.0/digiKam-7.9.0.tar.xz
4. Add dependencies if missing:
dnf builddep -y rpmbuild/SPECS/digikam.spec
5. Build and check:
rpmbuild -ba rpmbuild/SPECS/digikam.spec |& tee build.log
echo $?
grep error: build.log
OK, so this error persists:
/usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProductMMA.h: In function 'Eigen::internal::storeAccumulator<Eigen::internal::blas_data_mapper<double, long, 0, 0, 1>, long, double __vector(2), 2l>(long, long, Eigen::internal::blas_data_mapper<double, long, 0, 0, 1> const&, double __vector(2) const&, __vector_quad*)void':
/usr/include/eigen3/Eigen/src/Core/util/BlasUtil.h:227:46: error: inlining failed in call to 'always_inline' 'Eigen::internal::blas_data_mapper<double, long, 0, 0, 1>::storePacketBlock<double __vector(2), 4>(long, long, Eigen::internal::PacketBlock<double __vector(2), 4> const&) constvoid': target specific option mismatch
and I think that's because part of the fix was only applied to GCC 12:
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059#c34>:
"I don't think the r12-6219 commit qualifies for backporting."
This comment <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059#c35>
mentions a few workarounds. Maybe disabling LTO on ppc64le would help as well.
So I don't think I can backport a fix for this one, sorry.