From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Tom Rini <trini@konsulko.com>, Bin Meng <bmeng.cn@gmail.com>,
Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] libfdt: Tidy up pylibfdt build rule
Date: Fri, 26 Mar 2021 19:08:07 +1300 [thread overview]
Message-ID: <CAPnjgZ14BLLoKfdcETcpyahwBwBs_Z7MUG17cOyb15Nzkmcb7w@mail.gmail.com> (raw)
In-Reply-To: <20210326040208.878820-2-sjg@chromium.org>
On Fri, 26 Mar 2021 at 17:02, Simon Glass <sjg@chromium.org> wrote:
>
> At present the build rule for pylibfdt depends on _libfdt.so but modern
> Python versions add a different suffix to the output file, resulting in
> something like _libfdt.cpython-38-x86_64-linux-gnu.so
>
> The result is that pylibfdt is rebuilt every time.
>
> Rename the file the standard name so that the rule works correctly. Also
> add libfdt.py to the dependencies, so that file is always created if
> missing.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v3:
> - Make the rm silent
> - Use a single build rule to avoid building two pylibfdts in parallel
>
> Changes in v2:
> - Adjust tag so this patch doesn't got to dtc list
>
> scripts/dtc/pylibfdt/Makefile | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
Applied to u-boot-dm/next
(replacing v2)
prev parent reply other threads:[~2021-03-26 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 4:02 [PATCH v3 1/6] libfdt: Tidy up pylibfdt build rule Simon Glass
2021-03-26 6:08 ` Simon Glass [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=CAPnjgZ14BLLoKfdcETcpyahwBwBs_Z7MUG17cOyb15Nzkmcb7w@mail.gmail.com \
--to=sjg@chromium.org \
--cc=bmeng.cn@gmail.com \
--cc=devicetree-compiler@vger.kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=yamada.masahiro@socionext.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).