From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
yamada.masahiro@socionext.com, michal.lkml@markovi.net
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] scripts : mksysmap : NM variable missed the value,so fixed
Date: Thu, 17 Oct 2019 08:48:04 -0700 [thread overview]
Message-ID: <265d9be5-217d-3f67-ba94-095efdcf5787@infradead.org> (raw)
In-Reply-To: <20191017102506.22192-1-unixbhaskar@gmail.com>
On 10/17/19 3:25 AM, Bhaskar Chowdhury wrote:
> This patch will provide the missing value for NM variable.
>
Hi,
Does this patch fix some build error that you have encountered?
If so, please describe it and how to cause it.
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> TO all,
> Adjusted the subject line, missed in previous one,sorry
>
> scripts/mksysmap | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/mksysmap b/scripts/mksysmap
> index a35acc0d0b82..4b2f45c45f14 100755
> --- a/scripts/mksysmap
> +++ b/scripts/mksysmap
> @@ -40,5 +40,5 @@
> # 'W' or 'w'. __crc_ are 'A' and placed in the middle
> # so we just ignore them to let readprofile continue to work.
> # (At least sparc64 has __crc_ in the middle).
> -
> +NM=$(which nm)
That's not the POSIX way to do that. It should be
NM=$(command -v nm)
But why is this needed at all?
The top-level Makefile exports the NM variable (and many more) to scripts
that it calls.
> $NM -n $1 | grep -v '\( [aNUw] \)\|\(__crc_\)\|\( \$[adt]\)\|\( .L\)' > $2
> --
> 2.21.0
>
--
~Randy
next prev parent reply other threads:[~2019-10-17 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 10:25 Bhaskar Chowdhury
2019-10-17 15:48 ` Randy Dunlap [this message]
2019-10-17 17:10 ` Bhaskar Chowdhury
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=265d9be5-217d-3f67-ba94-095efdcf5787@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=torvalds@linux-foundation.org \
--cc=unixbhaskar@gmail.com \
--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
all inboxes | Powered by JetHome®