Re: [OE-core] [PATCH v2] u-boot: upgrade 2025.04 -> 2025.07

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Thu, Jul 17, 2025 at 10:19:45AM +0200, Mathieu Dubois-Briand wrote:
> On Wed Jul 16, 2025 at 10:04 AM CEST, Mikko Rapeli via lists.openembedded.org wrote:
> > From: Fabio Estevam <festevam@gmail.com>
> >
> > Upgrade to U-Boot 2025.07. Added patch for build race condition.
> > Removed qemu KVM USB workaround since issue is fixed upstream.
> >
> > Signed-off-by: Fabio Estevam <festevam@gmail.com>
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> >  ...-Makefile.lib-fix-_efi.so-dependency.patch | 116 ++++++++++++++++++
> >  .../u-boot/files/disable_CONFIG_USB.cfg       |   1 -
> >  meta/recipes-bsp/u-boot/u-boot-common.inc     |   7 +-
> >  ...ols_2025.04.bb => u-boot-tools_2025.07.bb} |   0
> >  .../{u-boot_2025.04.bb => u-boot_2025.07.bb}  |   4 +-
> >  5 files changed, 123 insertions(+), 5 deletions(-)
> >  create mode 100644 meta/recipes-bsp/u-boot/files/0001-Makefile-scripts-Makefile.lib-fix-_efi.so-dependency.patch
> >  delete mode 100644 meta/recipes-bsp/u-boot/files/disable_CONFIG_USB.cfg
> >  rename meta/recipes-bsp/u-boot/{u-boot-tools_2025.04.bb => u-boot-tools_2025.07.bb} (100%)
> >  rename meta/recipes-bsp/u-boot/{u-boot_2025.04.bb => u-boot_2025.07.bb} (64%)
> >
> > v2: added upstreamed patch to fix build race conditon, removed qemu kvm workaround
> >     fixed upstream. Would be nice to check if builds now pass.
> >
> > v1: https://lists.openembedded.org/g/openembedded-core/message/220004
> >
> 
> Hi Mikko, Fabio,
> 
> Thanks for the new version, I really had some hope, but it looks like we
> still have a similar fail:
> 
> ERROR: u-boot-1_2025.07-r0 do_compile: oe_runmake failed
> ...
> | arm-poky-linux-gnueabi-ld.bfd: cannot find arch/arm/lib/lib.a: No such file or directory
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2123
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1971
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1907

I still did not manage to reproduce these but added delays to some more linker
calls which hopefully exposed the same issues. Fixes submitted upstream
and are in v3.

Cheers,

-Mikko