From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/imx6slevk: Bump U-Boot version
Date: Thu, 20 Dec 2018 14:54:11 -0200 [thread overview]
Message-ID: <20181220165412.7982-1-festevam@gmail.com> (raw)
U-Boot 2017.11 has the following build issue:
MKIMAGE u-boot-dtb.imx
Error: No BOOT_FROM tag in board/freescale/mx6slevk/imximage.cfg.cfgtmp
arch/arm/mach-imx/Makefile:86: recipe for target 'u-boot-dtb.imx' failed
make[2]: *** [u-boot-dtb.imx] Error 1
Makefile:907: recipe for target 'u-boot-dtb.imx' failed
make[1]: *** [u-boot-dtb.imx] Error 2
make[1]: *** Waiting for unfinished jobs....
This issue has been fixed by commit f916757300c1 ("imx: Create
distinct pre-processed mkimage config files"), which landed in
U-Boot 2018.05.
Bump the U-Boot version to fix this build error.
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/136980040
Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
configs/imx6slevk_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/imx6slevk_defconfig b/configs/imx6slevk_defconfig
index be4b42e88e..90a02964e7 100644
--- a/configs/imx6slevk_defconfig
+++ b/configs/imx6slevk_defconfig
@@ -11,7 +11,7 @@ BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BOARDNAME="mx6slevk"
BR2_TARGET_UBOOT_CUSTOM_VERSION=y
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.11"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2018.11"
BR2_TARGET_UBOOT_FORMAT_IMX=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
--
2.17.1
next reply other threads:[~2018-12-20 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 16:54 Fabio Estevam [this message]
2018-12-20 16:54 ` [Buildroot] [PATCH 2/2] configs/freescale_imx7dsabresd: Apply upstream U-Boot fix Fabio Estevam
2018-12-21 13:59 ` Peter Korsgaard
2019-01-01 15:29 ` Peter Korsgaard
2018-12-21 13:58 ` [Buildroot] [PATCH 1/2] configs/imx6slevk: Bump U-Boot version Peter Korsgaard
2019-01-01 15:28 ` Peter Korsgaard
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=20181220165412.7982-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.