On 09. 08. 20 0:02, Jeff Law wrote:
For any package which was failing and LTO appeared to be a factor, I've assigned
the package's associated FTBFS BZ to me to address the LTO component. Some of
those I've already fixed and either closed the BZ or handed it back to the
default assignee for non-LTO issues that need to be resolved.
Thus if you have a package on the failing packages list and its still failing,
it's unlikely to be an LTO issue. I don't mind if you reach out, but start from
the assumption LTO isn't the triggering event. You can use %define _lto_cflags
%{nil} in your .spec file to disable LTO for testing purposes.
Thank you Jeff so very much for doing this!
I've assigned https://bugzilla.redhat.com/show_bug.cgi?id=1865257 to you as well
in the spirit of what you've said. The failure is workarounded with %global
_lto_cflags %{nil} now.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
