Re: ppc64le build failures in the mass rebuild

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2022-01-31 at 15:06 +0000, Mark E. Fuller wrote:
> My spec for cantera currently has an "excludearch" for ppc64le since
> the rawhide builds were failing - should I drop this allow for the
> releng tools to automatically find and rebuild it?

I'm not from releng team , I don't know if releng will do it or not, I
just suggest ...
But anyway, if you got a successful build, the script won't work ,
because just find packages that don't have any successful build since
the mass rebuild started, so in your case, you have to do yourself .

I suggest that you edit your spec and try a scratch build in koji just
on ppc64le arch with : 

fedpkg scratch-build --srpm --arch=ppc64le



> Thanks
> 
> 31 Jan 2022 16:47:07 Sérgio Basto <sergio@xxxxxxxxxx>:
> 
> > On Mon, 2022-01-31 at 13:36 +0100, Dan Horák wrote:
> > > On Mon, 31 Jan 2022 12:04:08 +0000
> > > Sérgio Basto <sergio@xxxxxxxxxx> wrote:
> > > 
> > > > On Mon, 2022-01-31 at 11:12 +0100, Dan Horák wrote:
> > > > > Hi,
> > > > > 
> > > > > as there are still a number of ppc64le build failures from
> > > > > the mass
> > > > > rebuild, please make the FTBFS bugs block the "PPCTracker" so
> > > > > we
> > > > > know
> > > > > about them.
> > > > > 
> > > > > Here is what we know so far
> > > > > - segfaulting ICE with "during RTL pass: final" or not being
> > > > > able
> > > > > to
> > > > > assemble the sources, those should be fixed in gcc-12.0.1-
> > > > > 0.3.fc36,
> > > > > so
> > > > > a rebuild should fix them
> > > > 
> > > > In resume, I think all failed builds , should be resubmitted
> > > > again.
> > > 
> > > it already happened in the 2nd run of the mass rebuild, I am
> > > mentioning
> > > it here mainly for completeness and in case someone will still
> > > hit it.
> > > 
> > 
> > yes I'm talking about a 3rd run , since is just resubmit the builds
> > that still failing , in https://pagure.io/releng we have the script
> > find_failures.py that can do that job ...
> > 
> > 
> > > 
> > >                 Dan
> > > 
> > > > 
> > > > 
> > > > > - issues with "__LDBL_REDIR1_DECL", they are caused by the
> > > > > bundled
> > > > > gnulib not being compatible with the installed glibc, a fix
> > > > > is to
> > > > > replace the bundled cdefs.h with more recent one
> > > > > (
> > > > > https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/cdefs.h;h=44d3826bca9f6f84f862acf1035408a587fac71d;hb=HEAD
> > > > > ),
> > > > > seen eg in lftp
> > > > > (https://bugzilla.redhat.com/show_bug.cgi?id=2045780)
> > > > > or dhcpd-pools
> > > > > (https://bugzilla.redhat.com/show_bug.cgi?id=2045310)
> > > > > 
> > > > > - various "long double" related issues, some might be fixed
> > > > > by
> > > > > building
> > > > > in proper order, but some will need further investigation, a
> > > > > corner
> > > > > case in libffi should be fixed in
> > > > > https://src.fedoraproject.org/rpms/libffi/pull-request/6
> > > > > 
> > > > > - various "vector" related issues/ICE, for example in cantera
> > > > > or
> > > > > mame
> > > > > 
> > > > > - libtool de-duplicating internal libs, when it shouldn't,
> > > > > like
> > > > > /usr/bin/ld: /usr/lib/gcc/ppc64le-redhat-
> > > > > linux/12/libgcc.a(float128-
> > > > > ifunc.o):
> > > > > (.data+0x0): undefined reference to
> > > > > `__parse_hwcap_and_convert_at_platform',
> > > > > this is a generic problem, a fix is proposed in
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2047389
> > > > > and workaround is
> > > > > https://src.fedoraproject.org/rpms/codeblocks/c/c8f36775a26f79d598e886a82460d1453871af20?branch=rawhide
> > > > > 
> > > > > - something else?
> > > > > 
> > > > > 
> > > > >         Thanks,
> > > > > 
> > > > >                 Dan
> > > > > _______________________________________________
> > > > > 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
> > > > > Do not reply to spam on the list, report it:
> > > > > https://pagure.io/fedora-infrastructure
> > > > 
> > > > -- 
> > > > Sérgio M. B.
> > > > _______________________________________________
> > > > 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
> > > > Do not reply to spam on the list, report it:
> > > > https://pagure.io/fedora-infrastructure
> > > _______________________________________________
> > > 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
> > > Do not reply to spam on the list, report it:
> > > https://pagure.io/fedora-infrastructure
> > 
> > -- 
> > Sérgio M. B.
> > _______________________________________________
> > 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
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> _______________________________________________
> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

-- 
Sérgio M. B.
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux