On Fri, 6 Oct 2023 at 07:38, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
On Fri, Oct 06, 2023 at 12:23:09PM +0100, Richard W.M. Jones wrote:
> On Fri, Oct 06, 2023 at 10:19:22AM +0100, Richard W.M. Jones wrote:
> > On Fri, Oct 06, 2023 at 08:48:52AM +0100, Richard W.M. Jones wrote:
> > > On Thu, Oct 05, 2023 at 10:03:59AM +0100, Richard W.M. Jones wrote:
> > > > Over the next few days I'm going to rebuild all OCaml packages in
> > > > Rawhide for OCaml 5.1, plus some non-OCaml packages that have OCaml
> > > > bindings.
> > > >
> > > > OCaml 5.1 is basically a small point release, but it does add back
> > > > native code support for riscv64 and s390x. The only remaining
> > > > architecture that hasn't been updated for OCaml 5 (and is therefore
> > > > still using the bytecode interpreter) is ppc64le.
> > >
> > > I think the builds are complete, except one which is running now.
> > >
> > > Only swig failed to build but that appears to be a general FTBFS bug:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2242372
> > >
> > > I'll submit an update later today once I've done a few more checks.
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2023-f0270d1637
>
> ELN builds are failing because they need to be done in build order,
> not in random or alphabetical order or whatever ELN uses, so that's a
> thing ...
Actually it's worse. Because this build of ocaml:
https://koji.fedoraproject.org/koji/taskinfo?taskID=107128822
was built before ocaml-srpm-macros was updated, it is being built
wrongly. The s390x build.log contains "--disable-native-compiler" but
it should be the opposite since native compilation is now supported.
Now partly this is a mistake in the spec file which should BR
ocaml-srpm-macros >= 9 (I'll fix that shortly), but partly this is
caused by the wrong build ordering of ELN.
If they are using the standard mass rebuild method, it is just feeding everything in alphabetical order, but it may still get 'reordered' somewhat by koji. I believe the main problem is that no one has ever hacked any sort of 'build recipe' to koji for it to 'know' that things need specific build orders or bootstrap instructions. Instead that has been left to the 'maintainers' of the packages because in general most of them required a lot of specific knowledge of the code to do right (or various maintainers do not want ANYONE ELSE to touch their package.) [Recipes got pulled into modularity but you also got all the rest of modularity also which was not what many maintainers wanted either]
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren_______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
