Fedora Account System
Red Hat Associate
Red Hat Customer
Please branch and build movit in epel9. If you do not wish to maintain movit in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/movit/addgroup and grant it commit access, or collaborator access on epel* branches.
https://koji.fedoraproject.org/koji/taskinfo?taskID=96591025 build failed on ppc64le , let me know if you have a fix , Thanks
This looks like a bug in eigen3: /usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProductCommon.h:215:28: error: inlining failed in call to 'always_inline' 'Eigen::internal::ploadRhs<float, float __vector(4)>(float const*)float __vector(4)': target specific option mismatch 215 | EIGEN_ALWAYS_INLINE Packet ploadRhs(const Scalar* rhs) | ^~~~~~~~ In file included from /usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProduct.h:38, from /usr/include/eigen3/Eigen/Core:350, from /usr/include/eigen3/Eigen/Dense:1, from deconvolution_sharpen_effect.cpp:5: /usr/include/eigen3/Eigen/src/Core/arch/AltiVec/MatrixProductMMA.h:128:34: note: called from here 128 | rhsV = ploadRhs<Scalar, Packet>((const Scalar*)(rhs)); | ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:127: deconvolution_sharpen_effect.lo] Error 1 make: *** Waiting for unfinished jobs....
Looks like bug 1996330 is this issue. Trying to figure out a workaround.
Alright, putting this at the top of the movit spec fixes the build: %if 0%{?el9} # Disable LTO for ppc64le to work around build failures # Cf. https://bugzilla.redhat.com/show_bug.cgi?id=1996330 %ifarch ppc64le %global _lto_cflags %{nil} %endif %endif
FEDORA-EPEL-2023-65804a8f90 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-65804a8f90
FEDORA-EPEL-2023-65804a8f90 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.