Thank you for the suggestions. I'll test reducing the debuginfo. However I still believe something else is in play, as such errors are normally very rare. The package has already been built without issues; it was the F35 mass rebuild which only bumped release, after which I noticed the FTBFS.
I also maintain a mysql module based on the same code. That's a lot of builds already, so I would likely spot build issues, if they would occur often. Is there a way to check how much resources the KOJI build actually consumed ? Michal -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Tue, Aug 3, 2021 at 11:44 AM Vitaly Zaitsev via devel <[email protected]> wrote: > > On 03/08/2021 11:31, Lukas Javorsky wrote: > > And is there any suggested way how to handle this situation? > > Special hacks for ARMv7: > > 1. Build in one thread. > 2. Reduce debug info: -g -> -g1 or even -g0. > > > Some spec build macro or something? > > %ifarch %{arm} > %global optflags %(echo %{optflags} | sed 's/-g /-g0 /') > %endif > > -- > Sincerely, > Vitaly Zaitsev ([email protected]) > _______________________________________________ > devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
