u-boot.git/Makefile, branch v2025.10-rc4

Prepare v2025.10-rc4

2025-09-08T16:17:59Z

Signed-off-by: Tom Rini

Prepare v2025.10-rc3

2025-08-25T19:06:38Z

Signed-off-by: Tom Rini

Prepare v2025.10-rc2

2025-08-11T19:47:46Z

Signed-off-by: Tom Rini

Makefile: Remove expansion of undefined variable

2025-08-05T00:23:16Z

The U-Boot environment was previously stored in the boot loader stream using ldr, but it has been replaced by the default environment built into the U-Boot executable or an environment on external storage Fixes: ea3310e8aafa ("Blackfin: Remove") Signed-off-by: Philip Molloy Reviewed-by: Greg Malysa

Makefile: add dependency from lib to arch/$(ARCH)/lib

2025-08-01T16:56:22Z

Top level Makefile starts separate "make" processes for each each subdirectory. lib/efi_loader apps now depend on lib.a from arch/$(ARCH)/lib if CONFIG_USE_PRIVATE_LIBGCC is enabled which creates a race conditions since dependency from lib/efi_loader EFI apps to arch/$(ARCH)/lib/lib.a is not explicit: arm-poky-linux-gnueabi-ld.bfd: cannot find arch/arm/lib/lib.a: No such file or directory make[3]: *** [scripts/Makefile.lib:512: lib/efi_loader/testapp_efi.so] Error 1 This error was seen on yocto/OE-core CI builds after u-boot 2025.07 update: https://lists.openembedded.org/g/openembedded-core/message/220004 https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/2914600/raw_inline | rm -f lib/efi_loader/built-in.o; arm-poky-linux-gnueabi-ar cDPrsT lib/efi_loader/built-in.o lib/efi_loader/efi_bootmgr.o lib/efi_loader/efi_bootbin.o lib/efi_loader /efi_boottime.o lib/efi_loader/efi_helper.o lib/efi_loader/efi_console.o lib/efi_loader/efi_device_path.o lib/efi_loader/efi_device_path_to_text.o lib/efi_loader/efi_device_ path_utilities.o lib/efi_loader/efi_dt_fixup.o lib/efi_loader/efi_fdt.o lib/efi_loader/efi_file.o lib/efi_loader/efi_hii.o lib/efi_loader/efi_hii_config.o lib/efi_loader/efi _image_loader.o lib/efi_loader/efi_load_options.o lib/efi_loader/efi_memory.o lib/efi_loader/efi_root_node.o lib/efi_loader/efi_runtime.o lib/efi_loader/efi_setup.o lib/efi_ loader/efi_string.o lib/efi_loader/efi_unicode_collation.o lib/efi_loader/efi_var_common.o lib/efi_loader/efi_var_mem.o lib/efi_loader/efi_variable.o lib/efi_loader/efi_var_ file.o lib/efi_loader/efi_watchdog.o lib/efi_loader/efi_disk.o lib/efi_loader/efi_net.o lib/efi_loader/efi_smbios.o lib/efi_loader/efi_load_initrd.o lib/efi_loader/efi_confo rmance.o | arm-poky-linux-gnueabi-ld.bfd -nostdlib -zexecstack -znocombreloc -znorelro --no-warn-rwx-segments -L /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st- 3119200/tmp/work/beaglebone_yocto-poky-linux-gnueabi/u-boot/2025.07/sources/u-boot-2025.07 -T arch/arm/lib/elf_arm_efi.lds -shared -Bsymbolic -s lib/efi_loader/helloworld.o lib/efi_loader/efi_crt0.o lib/efi_loader/efi_reloc.o lib/efi_loader/efi_freestanding.o arch/arm/lib/lib.a -o lib/efi_loader/helloworld_efi.so | arm-poky-linux-gnueabi-ld.bfd: cannot find arch/arm/lib/lib.a: No such file or directory | make[3]: *** [scripts/Makefile.lib:512: lib/efi_loader/helloworld_efi.so] Error 1 The different "make" processes share common scripts/Makefile.build and scripts/Makefile.libs but since they are separate processes the Makefile rules can't add a dependency from lib/uefi_loader targets to arch/$(ARCH)/lib/lib.a. Or the file level dependency can be added but then "make" produces a too sparse error message which does not mention that one of the dependencies like arch/$(ARCH)/lib/lib.a was not found: make[3]: *** No rule to make target 'lib/efi_loader/helloworld.efi', needed by '__build'. Stop. Fix this dependency problem by building arch/$(ARCH)/lib before lib if CONFIG_USE_PRIVATE_LIBGCC was enabled. To reproduce the race condition more reliably, add a "sleep 10" delay before linker command cmd_link_l_target with 2025.07 or to $(lib-target): target in scripts/Makefile.build with master branch after Kbuild update. Fixes: 43d43241d1c9 ("scripts/Makefile.lib: add PLATFORM_LIBGCC to efi linking") Cc: Adriano Cordova Cc: Fabio Estevam Signed-off-by: Mikko Rapeli Reviewed-by: Fabio Estevam

Prepare v2025.10-rc1

2025-07-29T00:23:01Z

Signed-off-by: Tom Rini

efi: Rename the lib/efi directory

2025-07-26T05:29:31Z

This directory was created when U-Boot gained the ability to run as an EFI app in 2015. Since then the EFI-loader feature has been added. The code in lib/efi is not actually used by the loader, so the name is confusing. Rename the directory to efi_client to indicate that it includes files just for U-Boot being a client of EFI, i.e. the EFI app and stub. Signed-off-by: Simon Glass

kbuild: Don't mandate gcc as the host compiler

2025-07-18T18:22:24Z

Systems that use clang may not have gcc installed. Set HOSTCC to cc and HOSTCXX to c++ like we did before to make those systems work again. Fixes: 5f520875bdf0 ("kbuild: Bump the build system to 5.1") Signed-off-by: Mark Kettenis

kbuild: Avoid including architecture-specific Makefile twice

2025-07-12T15:49:26Z

Stranges errors are observed when building U-Boot master for almost any RISC-V board, the messages are in two types, one is about duplicated symbols, u-boot/arch/riscv/cpu//mtrap.S:32: multiple definition of `trap_entry'; arch/riscv/cpu/mtrap.o: u-boot/arch/riscv/cpu//mtrap.S:32: first defined here and the other is fixdep's complaint about missing dependency files, fixdep: error opening file: arch/riscv/cpu/.mtrap.o.d: No such file or directory fixdep: error opening file: arch/riscv/cpu//.start.o.d: No such file or directory where the latter could only be reproduced when building parallelly. Both the two types of errors are about files in arch/riscv/cpu, and there's a suspicious slash character in the reported path. Looking through RISC-V-specific Makefiles, there's only one place that may expand to such a path, libs-y += arch/riscv/cpu/$(CPU)/ The right hand expands to "arch/riscv/cpu//" if $(CPU) isn't defined at the time of including. With some debug statement added to arch/riscv/Makefile, the output proves that arch/riscv/Makefile is included twice, once with $(CPU) undefined and once defined correctly according to CONFIG_SYS_CPU. Futher bisecting shows an extra include statement against arch/$(SRCARCH)/Makefile is added in earlier bump of Kbuild system. But the statement is evaluated before config.mk is included and definition of $(CPU), causing objects in arch/riscv/cpu/ are built and linked twice (once as "arch/riscv/cpu/*", and once as "arch/riscv/cpu//*"), resulting in the error. Let's simply remove the extra include to fix these nasty errors. For config targets, bumping Kbuild also introduced a new include to arch/$(SRCARCH)/Makefile, which is removed as well for consistency. Fixes: 5f520875bdf ("kbuild: Bump the build system to 5.1") Signed-off-by: Yao Zi Reviewed-by: Ilias Apalodimas Tested-by: Fabio Estevam Tested-by: Bryan Brattlof

makefile: Adjust distclean to remove .binman_stamp file

2025-07-10T14:41:20Z

Remove the .binman_stamp file during distclean Signed-off-by: Magnus Damm