From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] configs/zynq_zed: uboot: bump to xilinx-v2018.2 (fixes build)
Date: Thu, 6 Sep 2018 21:31:56 +0200 [thread overview]
Message-ID: <20180906213156.7936ae96@windsurf> (raw)
In-Reply-To: <20180828080059.21788-1-luca@lucaceresoli.net>
Hello,
On Tue, 28 Aug 2018 10:00:57 +0200, Luca Ceresoli wrote:
> 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.
>
> [Run-time tested]
> Tested-by: Luca Ceresoli <luca@lucaceresoli.net>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> ---
> configs/zynq_zed_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
All applied to next. Peter is about to release 2018.08, so I didn't
want to merge into master. The problem anyway affects lots of
defconfigs, and Peter will document it in the CHANGES file.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-06 19:31 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 ` [Buildroot] [PATCH 2/3] configs/zynq_zc706: " Luca Ceresoli
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 [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=20180906213156.7936ae96@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox