Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board/ci20: Fix U-Boot build failure
Date: Sun, 1 Apr 2018 16:05:55 +0200	[thread overview]
Message-ID: <20180401160555.36587bd1@windsurf> (raw)
In-Reply-To: <20180401135035.29655-1-ezequiel@collabora.com>

Hello,

On Sun,  1 Apr 2018 10:50:35 -0300, Ezequiel Garcia wrote:
> Given there is no upstream U-Boot for CI20, the defconfig
> sets an ancient version, with old libfdt headers.
> 
> Enable DTC, so U-Boot can pick Buildroot's libfdt headers
> instead of those installed by the host.
> 
> Fixes multiple errors looking like this:
> 
> In file included from ../include/libfdt.h:54:0,
>                  from fdt_host.h:11,
>                  from mkimage.h:22,
>                  from aisimage.c:8:
> /usr/include/libfdt_env.h:70:30: error: conflicting types for ?fdt64_t?
>  typedef uint64_t FDT_BITWISE fdt64_t;

Which Buildroot version are you using ? We fixed errors like that
recently, and I built ci20_defconfig yesterday, and it worked fine for
me.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

       reply	other threads:[~2018-04-01 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180401135035.29655-1-ezequiel@collabora.com>
2018-04-01 14:05 ` Thomas Petazzoni [this message]
     [not found]   ` <1522621901.1665.1.camel@collabora.com>
2018-04-01 22:42     ` [Buildroot] [PATCH] board/ci20: Fix U-Boot build failure Thomas Petazzoni
2018-04-01 22:58       ` Ezequiel Garcia
2018-04-01 22:44     ` Ezequiel Garcia

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=20180401160555.36587bd1@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