From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>
Date: Tue, 6 Mar 2018 09:27:43 -0500 [thread overview]
Message-ID: <20180306142743.GI22474@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <1520325595.2018.23.camel@bootlin.com>
On Tue, Mar 06, 2018 at 09:39:55AM +0100, Paul Kocialkowski wrote:
> Hi,
>
> On Mon, 2018-03-05 at 01:20 +0900, Masahiro Yamada wrote:
> > Thomas reported U-Boot failed to build host tools if libfdt-devel
> > package is installed because tools include libfdt headers from
> > /usr/include/ instead of using internal ones.
>
> Sorry for being late to the party here, but isn't this issue fixed by
> the patch I sent a few days ago "tools: Include U-Boot libfdt headers
> from their actual path": https://patchwork.ozlabs.org/patch/880924/ ?
>
> I doubt we need to keep both changes here. What do you think?
I did both, intentionally. This patch fails for me on host tools,
without your patch. However, trying harder to match the Linux kernel
structure will be helpful long term I think.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180306/1cf5e9a9/attachment.sig>
next prev parent reply other threads:[~2018-03-06 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 16:20 [U-Boot] [PATCH] libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h> Masahiro Yamada
2018-03-04 16:47 ` christophe leroy
2018-03-05 18:53 ` [U-Boot] " Tom Rini
2018-03-06 8:39 ` [U-Boot] [PATCH] " Paul Kocialkowski
2018-03-06 14:27 ` Tom Rini [this message]
2018-03-06 15:29 ` Masahiro Yamada
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=20180306142743.GI22474@bill-the-cat.ec.rr.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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