From: Thomas Petazzoni <thomas.petazzoni-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
To: Geoff Levand <geoff-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: buildroot-9GAsQqxh4YTR7s880joybQ@public.gmane.org,
Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v1] dtc: Add set-ldshared.patch
Date: Sat, 28 Jul 2018 15:43:29 +0200 [thread overview]
Message-ID: <20180728154329.0bafffec@windsurf> (raw)
In-Reply-To: <20180728145647.70ac1d52@windsurf>
Hello,
On Sat, 28 Jul 2018 14:56:47 +0200, Thomas Petazzoni wrote:
> Are you sure your patch is fixing the host-dtc build issues ?
>
> I am seeing two different build issues:
>
> - One for host-dtc, which looks like this:
[...]
> - One for dtc, which looks like this:
Since all those problems are due to pylibfdt, which is new since 1.4.5,
and that we don't use in Buildroot, I applied a simpler fix: pass
NO_PYTHON=1 so that we don't build the Python support, even if the
necessary dependencies are found.
See:
https://git.buildroot.org/buildroot/commit/?id=b50c95e914c6366e30145378fa82f286d4412c51
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-28 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28d7fee033a5e5ef512c02d5291d20b1d19fdbbf.1532460521.git.geoff@infradead.org>
[not found] ` <20180727110728.300c06e2@windsurf>
2018-07-27 22:23 ` [PATCH v1] dtc: Add set-ldshared.patch Geoff Levand
[not found] ` <f1e71e0d-6728-78d1-0431-c1e2846ab885-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2018-07-28 12:56 ` Thomas Petazzoni
2018-07-28 13:43 ` Thomas Petazzoni [this message]
2018-07-30 14:46 ` Geoff Levand
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=20180728154329.0bafffec@windsurf \
--to=thomas.petazzoni-ldxbnhwyfcjbdgjk7y7tuq@public.gmane.org \
--cc=buildroot-9GAsQqxh4YTR7s880joybQ@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geoff-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).