On Thu, 2022-01-27 at 14:00 +0100, Thomas Haller wrote: > On Thu, 2022-01-27 at 11:09 +0100, Jakub Jelinek wrote: > > On Thu, Jan 27, 2022 at 10:32:22AM +0100, Thomas Haller wrote: > > > On Wed, 2022-01-26 at 23:57 +0100, Jakub Jelinek wrote: > > > > A new gcc with most importantly the > > > > https://gcc.gnu.org/PR104172 > > > > bug (that caused a lot of ppc64le failures) fixed and various > > > > other > > > > fixes (e.g. std::basic_string(std::nullptr_t) = deleted only > > > > done > > > > for C++23 etc.) is now in rawhide. > > > > > > > > Can rel-eng please retry all FTBS builds that failed on > > > > ppc64le? > > > > > > it appears to me, that this breaks build of NetworkManager: > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=81998774 > > > > > > > > > checking if gcc supports flag -fno-strict-aliasing in envvar > > > CFLAGS... yes > > > checking if gcc supports flag -flto -flto-partition=none in > > > envvar CFLAGS... no > > > configure: error: Link Time Optimization -flto is not > > > supported. > > > error: Bad exit status from /var/tmp/rpm-tmp.FQqAFe (%build) > > > > Apparently it was annobin (although it passed the test done during > > gcc.spec > > testing, apparently it was incompatible again). > > Florian has rebuilt it, so please just retry.
Hi, after a few days, it seems, the problem still exists in the buildroot for copr: https://copr.fedorainfracloud.org/coprs/networkmanager/NetworkManager-main/build/3288936/ Should we just wait longer and it solves itself? best, Thomas _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
