From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: Execute tools from objtree
Date: Wed, 2 Nov 2016 12:21:51 +0100 [thread overview]
Message-ID: <20161102112151.23159-1-marex@denx.de> (raw)
Always execute the tools from the build destination directory
and with a full path, otherwise we may get errors like this
(from OE-core):
| ERROR: oe_runmake failed
| cat ./Licenses/gpl-2.0.txt | gzip -9 -c | \
| tools/bin2header license_gzip > ./include/license.h
| /bin/sh: 2: tools/bin2header: not found
| tools/Makefile:256: recipe for target 'include/license.h' failed
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Tom Rini <trini@konsulko.com>
---
tools/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/Makefile b/tools/Makefile
index 421414b..7dacedb 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -247,14 +247,14 @@ HOST_EXTRACFLAGS += -include $(srctree)/include/libfdt_env.h \
__build: $(LOGO-y) $(LICENSE-y)
$(LOGO_H): $(obj)/bmp_logo $(LOGO_BMP)
- $(obj)/bmp_logo --gen-info $(LOGO_BMP) > $@
+ $(objtree)/bmp_logo --gen-info $(LOGO_BMP) > $@
$(LOGO_DATA_H): $(obj)/bmp_logo $(LOGO_BMP)
- $(obj)/bmp_logo --gen-data $(LOGO_BMP) > $@
+ $(objtree)/bmp_logo --gen-data $(LOGO_BMP) > $@
$(LICENSE_H): $(obj)/bin2header $(srctree)/Licenses/gpl-2.0.txt
cat $(srctree)/Licenses/gpl-2.0.txt | gzip -9 -c | \
- $(obj)/bin2header license_gzip > $(LICENSE_H)
+ $(objtree)/bin2header license_gzip > $(LICENSE_H)
# Let clean descend into subdirs
subdir- += env
--
2.9.3
next reply other threads:[~2016-11-02 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 11:21 Marek Vasut [this message]
2016-11-02 11:22 ` [U-Boot] [PATCH] tools: Execute tools from objtree Marek Vasut
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=20161102112151.23159-1-marex@denx.de \
--to=marex@denx.de \
--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