Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <pierre-loup.gosse@smile.fr>, <openembedded-core@lists.openembedded.org>
Cc: "Ross Burton" <ross.burton@arm.com>
Subject: Re: [OE-core] [PATCH v2 2/2] oe-selftest: uboot: add test for building U-Boot initial env binary
Date: Wed, 19 Nov 2025 18:41:13 +0100	[thread overview]
Message-ID: <DECUU0K7IT03.3ERKMFJR5CVH2@bootlin.com> (raw)
In-Reply-To: <20251117161239.1227164-2-pierre-loup.gosse@smile.fr>

On Mon Nov 17, 2025 at 5:12 PM CET, Pierre-loup GOSSE via lists.openembedded.org wrote:
> From: Pierre-Loup GOSSE <pierre-loup.gosse@smile.fr>
>
> This adds two new selftest cases `test_uboot_initial_env_binary` and
> `test_uboot_config_initial_env_binary` to verify the build of the U-Boot
> initial env binary with the mkimage tool.
>
> Signed-off-by: Pierre-Loup GOSSE <pierre-loup.gosse@smile.fr>
> Cc: Ross Burton <ross.burton@arm.com>
> ---

Hi Pierre-Loup,

Thanks for your patch.

It looks like this is failing when building on ARM machines:

2025-11-19 10:13:26,832 - oe-selftest - INFO - uboot.UBootTest.test_uboot_config_initial_env_binary (subunit.RemotedTestCase)
2025-11-19 10:13:26,836 - oe-selftest - INFO -  ... FAIL
...
ERROR: u-boot-1_2025.10-r0 do_compile: oe_runmake failed
ERROR: u-boot-1_2025.10-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/temp/run.do_compile.1762173' failed with exit code 1
...
|   aarch64-poky-linux-gcc  --sysroot=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/recipe-sysroot  -ffile-prefix-map=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/sources/u-boot-2025.10=/usr/src/debug/u-boot/2025.10  -ffile-prefix-map=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/build=/usr/src/debug/u-boot/2025.10  -ffile-prefix-map=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/recipe-sysroot=  -ffile-prefix-map=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/recipe-sysroot-native=  -E -Wall -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu11  -ffreestanding -fno-builtin -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -Wno-address-of-packed-member -O2 -fno-stack-protector -fno-delete-null-pointer-checks -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized -fmacro-prefix-map=/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/sources/u-boot-2025.10/= -gdwarf-4 -fstack-usage -Wno-format-nonliteral -Wno-address-of-packed-member -Wno-unused-but-set-variable -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -D__KERNEL__ -D__UBOOT__ -fomit-frame-pointer  -fno-toplevel-reorder -fno-dwarf2-cfi-asm -fpic -fno-common -march=core2 -m64 -D__x86_64__ -fdata-sections -ffunction-sections -fvisibility=hidden -pipe -Iinclude  -I/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/sources/u-boot-2025.10/include -I/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/sources/u-boot-2025.10/arch/x86/include -include /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/sources/u-boot-2025.10/include/linux/kconfig.h -nostdinc -isystem /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-3996856/tmp/work/qemuarm64-poky-linux/u-boot/2025.10/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../lib/aarch64-poky-linux/gcc/aarch64-poky-linux/15.2.0/include -DCONFIG_XPL_BUILD -DCONFIG_SPL_BUILD -DDO_DEPS_ONLY -dM include/config.h > spl/u-boot.cfg.tmp && { grep 'define CONFIG_' spl/u-boot.cfg.tmp | sed '/define CONFIG_IS_ENABLED(/d;/define CONFIG_IF_ENABLED_INT(/d;/define CONFIG_VAL(/d;' > spl/u-boot.cfg; rm spl/u-boot.cfg.tmp; } || { rm spl/u-boot.cfg.tmp; false; }
| aarch64-poky-linux-gcc: error: unrecognized command-line option '-m64'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2854

Can you have a look at the issue?

Thanks,
Mathieu

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



      reply	other threads:[~2025-11-19 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 16:12 [PATCH v2 1/2] u-boot: make initial environment binary image pierre-loup.gosse
2025-11-17 16:12 ` [PATCH v2 2/2] oe-selftest: uboot: add test for building U-Boot initial env binary pierre-loup.gosse
2025-11-19 17:41   ` Mathieu Dubois-Briand [this message]

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=DECUU0K7IT03.3ERKMFJR5CVH2@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pierre-loup.gosse@smile.fr \
    --cc=ross.burton@arm.com \
    /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