All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: Marek Vasut <marex@denx.de>,
	trini@konsulko.com,
	Otavio Salvador <otavio.salvador@ossystems.com.br>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 16/20] dtc: upgrade to 1.4.6
Date: Mon, 5 Feb 2018 16:52:02 +0200	[thread overview]
Message-ID: <7452a226-371f-7bcb-d183-8d22a69f8e11@linux.intel.com> (raw)
In-Reply-To: <cf9b1424-a148-fe3b-fc77-49b6c7b89e0f@linux.intel.com>

On 02/05/2018 12:42 PM, Alexander Kanavin wrote:
>>> /data/poky-tmp/master/work/beaglebone_yocto-poky-linux-gnueabi/u-boot/1_2018.01-r0/recipe-sysroot-native/usr/include/libfdt_env.h:70:30: 
>>>
>>> error: conflicting types for 'fdt64_t'
>>> |  typedef uint64_t FDT_BITWISE fdt64_t;
>>> |                               ^~~~~~~
>>> | In file included from <command-line>:0:0:
>>> |
>>> /data/poky-tmp/master/work/beaglebone_yocto-poky-linux-gnueabi/u-boot/1_2018.01-r0/git/include/libfdt_env.h:19:16: 
>>>
>>> note: previous declaration of 'fdt64_t' was here
>>> |  typedef __be64 fdt64_t;
>>> |                 ^~~~~~~
>>>
>>
>> I have a patch to u-boot which is fixing similar issue. see
>> see if this helps.
>>
>> https://gist.github.com/kraj/70d613d1ead4be98a5787928d8518434
>>
> 
> Thanks, I think u-boot upstream also has a fix for it. I'll check.

Unfortunately, latest u-boot upstream still fails in the same way. As I 
really have no idea about when system includes vs bundled includes 
should be used (and no way to test anything u-boot related), let's defer 
this update until either upstream takes care of this issue.

Alex



  reply	other threads:[~2018-02-05 14:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 18:01 [PATCH 01/20] oe-selftest: add a test for recipes without maintainers Alexander Kanavin
2018-02-01 18:01 ` [PATCH 02/20] rpm: update to 4.14.1 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 03/20] rpm: add a patch to help with Docker performance issues Alexander Kanavin
2018-02-01 18:01 ` [PATCH 04/20] openssl: update to 1.0.2n Alexander Kanavin
2018-02-01 18:01 ` [PATCH 05/20] webkitgtk: update to 2.18.6 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 06/20] epiphany: update to 3.26.5.1 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 07/20] p11-kit: take source code from official git Alexander Kanavin
2018-02-01 18:01 ` [PATCH 08/20] libnl: 3.2.29 -> 3.4.0 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 09/20] vala: update to 0.38.6 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 10/20] mpg123: update to 1.25.8 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 11/20] boost: update to 1.66.0 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 12/20] liburcu: update to 0.10.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 13/20] btrfs-tools: update to 4.14.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 14/20] libwebp: update to 0.6.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 15/20] iso-codes: update to 3.77 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 16/20] dtc: upgrade to 1.4.6 Alexander Kanavin
2018-02-04  8:31   ` Burton, Ross
2018-02-04 17:11     ` Khem Raj
2018-02-05 10:42       ` Alexander Kanavin
2018-02-05 14:52         ` Alexander Kanavin [this message]
2018-02-05 18:18           ` Khem Raj
2018-02-01 18:02 ` [PATCH 17/20] ffmpeg: update to 3.4.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 18/20] iputils: update to 20161105 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 19/20] babeltrace: update to 1.5.4 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 20/20] libmpc: fix upstream version check Alexander Kanavin
2018-02-01 18:33 ` ✗ patchtest: failure for "oe-selftest: add a test for re..." and 19 more Patchwork
2018-02-01 19:21   ` Alexander Kanavin
2018-02-01 20:41 ` [PATCH 01/20] oe-selftest: add a test for recipes without maintainers Paul Eggleton
2018-02-02 10:47   ` Alexander Kanavin

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=7452a226-371f-7bcb-d183-8d22a69f8e11@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@intel.com \
    --cc=trini@konsulko.com \
    /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.