From: Masahiro Yamada <masahiroy@kernel.org>
To: Michal Suchanek <msuchanek@suse.de>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] kbuild: dummy-tools: Add elfedit.
Date: Sun, 11 Apr 2021 03:12:40 +0900 [thread overview]
Message-ID: <CAK7LNAR-zdHLpp7eQ_PUG6PQMKUKh2m0b80NGSxnxuXhjyT=3g@mail.gmail.com> (raw)
In-Reply-To: <f6218ac526a04fa4d4406f935bcc4eb4a7df65c4.1617917438.git.msuchanek@suse.de>
On Fri, Apr 9, 2021 at 6:31 AM Michal Suchanek <msuchanek@suse.de> wrote:
>
> elfedit is used in Makefile
>
> Makefile:GCC_TOOLCHAIN_DIR := $(dir $(shell which $(CROSS_COMPILE)elfedit))
>
> which causes this error getting printed
>
> which: no elfedit in (./scripts/dummy-tools)
I am OK with this patch, but how did you reproduce it?
>
> Add elfedit to dummy-tools to avoid this error.
>
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> ---
> scripts/dummy-tools/elfedit | 1 +
> 1 file changed, 1 insertion(+)
> create mode 120000 scripts/dummy-tools/elfedit
>
> diff --git a/scripts/dummy-tools/elfedit b/scripts/dummy-tools/elfedit
> new file mode 120000
> index 000000000000..c0648b38dd42
> --- /dev/null
> +++ b/scripts/dummy-tools/elfedit
> @@ -0,0 +1 @@
> +ld
> \ No newline at end of file
> --
> 2.26.2
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2021-04-10 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 21:31 [PATCH 1/2] kbuild: dummy-tools: Add elfedit Michal Suchanek
2021-04-08 21:31 ` [PATCH 2/2] MAINTAINERS: add pattern for dummy-tools Michal Suchanek
2021-04-11 12:38 ` Masahiro Yamada
2021-04-10 18:12 ` Masahiro Yamada [this message]
2021-04-11 10:18 ` [PATCH 1/2] kbuild: dummy-tools: Add elfedit Michal Suchánek
2021-04-11 11:37 ` Masahiro Yamada
2021-04-11 20:03 ` Michal Suchánek
2021-04-16 19:22 ` Miguel Ojeda
2021-04-12 12:46 ` Michal Suchánek
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='CAK7LNAR-zdHLpp7eQ_PUG6PQMKUKh2m0b80NGSxnxuXhjyT=3g@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=msuchanek@suse.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;
as well as URLs for NNTP newsgroup(s).