All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] configs/zynq_zc706: uboot: bump to xilinx-v2018.2 (fixes build)
Date: Tue, 28 Aug 2018 10:00:58 +0200	[thread overview]
Message-ID: <20180828080059.21788-2-luca@lucaceresoli.net> (raw)
In-Reply-To: <20180828080059.21788-1-luca@lucaceresoli.net>

Bump to the most recent Xilinx release.

Fixes:
  .../output/host/include/libfdt_env.h:71:30: error: conflicting types for ?fdt64_t?
  .../output/host/include/libfdt_env.h:91:24: error: expected ?)? before ?x?
  .../output/host/include/libfdt.h:150:21: error: redefinition of ?fdt_offset_ptr_w?
...and many, many other similar errors.

[Build-tested only]
Tested-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
---
 configs/zynq_zc706_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/zynq_zc706_defconfig b/configs/zynq_zc706_defconfig
index 758069b30fe8..e8019177d2b8 100644
--- a/configs/zynq_zc706_defconfig
+++ b/configs/zynq_zc706_defconfig
@@ -20,7 +20,7 @@ BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/Xilinx/u-boot-xlnx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2017.3"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2018.2"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zc706"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
-- 
2.17.1

  reply	other threads:[~2018-08-28  8:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  8:00 [Buildroot] [PATCH 1/3] configs/zynq_zed: uboot: bump to xilinx-v2018.2 (fixes build) Luca Ceresoli
2018-08-28  8:00 ` Luca Ceresoli [this message]
2018-08-28  8:00 ` [Buildroot] [PATCH 3/3] configs/zynq_microzed: " Luca Ceresoli
2018-08-28 21:15 ` [Buildroot] [PATCH 1/3] configs/zynq_zed: " Thomas Petazzoni
2018-08-30 13:01   ` Luca Ceresoli
2018-09-06 19:31 ` Thomas Petazzoni

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=20180828080059.21788-2-luca@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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.