From: Thierry Reding <treding@nvidia.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org,
"Bjørn Forsman" <bjorn.forsman@gmail.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Michal Marek" <mmarek@suse.com>,
linux-pm@vger.kernel.org, "Kieran Bingham" <kieran@bingham.xyz>,
linux-kernel@vger.kernel.org, "Thomas Renninger" <trenn@suse.com>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] kbuild: use $(abspath ...) instead of $(shell cd ... && /bin/pwd)
Date: Mon, 21 Aug 2017 10:49:30 +0200 [thread overview]
Message-ID: <20170821084930.GA7678@ulmo> (raw)
In-Reply-To: <1503209051-16477-1-git-send-email-yamada.masahiro@socionext.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On Sun, Aug 20, 2017 at 03:04:11PM +0900, Masahiro Yamada wrote:
> Kbuild conventionally uses $(shell cd ... && /bin/pwd) idiom to get
> the absolute path of the directory because GNU Make 3.80, the minimal
> supported version at that time, did not support $(abspath ...) or
> $(realpath ...).
>
> Commit 37d69ee30808 ("docs: bump minimal GNU Make version to 3.81")
> dropped the GNU Make 3.80 support, so we are now allowed to use those
> make-builtin helpers.
>
> This conversion will provide better portability without relying on
> the pwd command or its location /bin/pwd.
>
> I am intentionally using $(realpath ...) instead $(abspath ...) in
> some places. The difference between the two is $(realpath ...)
> returns an empty string if the given path does not exist. It is
> convenient in places where we need to error-out if the makefile fails
> to create an output directory.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> Makefile | 12 ++++++------
> scripts/gdb/linux/Makefile | 2 +-
> tools/power/cpupower/Makefile | 2 +-
> tools/scripts/Makefile.include | 6 +++---
> 4 files changed, 11 insertions(+), 11 deletions(-)
This looks very similar to a patch I had written a long time ago:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-21 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 6:04 [PATCH] kbuild: use $(abspath ...) instead of $(shell cd ... && /bin/pwd) Masahiro Yamada
2017-08-21 8:49 ` Thierry Reding [this message]
2017-08-21 9:04 ` Masahiro Yamada
2017-08-31 23:52 ` 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=20170821084930.GA7678@ulmo \
--to=treding@nvidia.com \
--cc=acme@redhat.com \
--cc=bjorn.forsman@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jpoimboe@redhat.com \
--cc=kieran@bingham.xyz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=sam@ravnborg.org \
--cc=trenn@suse.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