From: Krzysztof Kozlowski <krzk@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andriin@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>,
Alexey Gladkov <gladkov.alexey@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Jessica Yu <jeyu@kernel.org>
Subject: [PATCH] kbuild: Fix cross compile link with ccache
Date: Mon, 6 May 2019 14:40:00 +0200 [thread overview]
Message-ID: <1557146400-12269-1-git-send-email-krzk@kernel.org> (raw)
Fix calling objcopy in case of cross compile environments:
ARCH="arm" CROSS_COMPILE="ccache arm-linux-gnueabi-" make
scripts/link-vmlinux.sh: line 211: ccache arm-linux-gnueabi-objcopy: command not found
Fixes: 6a26793a7891 ("moduleparam: Save information about built-in modules in separate file")
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
scripts/link-vmlinux.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 62b9fc561af7..42ea6f9264ef 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -208,7 +208,7 @@ modpost_link vmlinux.o
${MAKE} -f "${srctree}/scripts/Makefile.modpost" vmlinux.o
info MODINFO modules.builtin.modinfo
-"${OBJCOPY}" -j .modinfo -O binary vmlinux.o modules.builtin.modinfo
+${OBJCOPY} -j .modinfo -O binary vmlinux.o modules.builtin.modinfo
kallsymso=""
kallsyms_vmlinux=""
--
2.7.4
next reply other threads:[~2019-05-06 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 12:40 Krzysztof Kozlowski [this message]
2019-05-06 12:43 ` [PATCH] kbuild: Fix cross compile link with ccache Krzysztof Kozlowski
2019-05-06 14:10 ` 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=1557146400-12269-1-git-send-email-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=gladkov.alexey@gmail.com \
--cc=glebfm@altlinux.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 NNTP newsgroup(s).