Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <mikko.rapeli@linaro.org>, <openembedded-core@lists.openembedded.org>
Cc: "Fabio Estevam" <festevam@gmail.com>
Subject: Re: [OE-core] [PATCH v2] u-boot: upgrade 2025.04 -> 2025.07
Date: Thu, 17 Jul 2025 10:19:45 +0200	[thread overview]
Message-ID: <DBE6M18ID41K.956HRERV352W@bootlin.com> (raw)
In-Reply-To: <20250716080437.189201-1-mikko.rapeli@linaro.org>

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

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-07-17  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  8:04 [PATCH v2] u-boot: upgrade 2025.04 -> 2025.07 Mikko Rapeli
2025-07-17  8:19 ` Mathieu Dubois-Briand [this message]
2025-07-18  9:08   ` [OE-core] " Mikko Rapeli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DBE6M18ID41K.956HRERV352W@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=festevam@gmail.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox