diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2023-12-15 19:06:37 +0300 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2023-12-29 16:25:21 +0300 |
commit | 7beba04eb305393e3f8386390f25b4a9475f27f2 (patch) | |
tree | 8e35c7f8a4676e4468ebb7587e660ab0ddcadc61 /drivers/leds/Kconfig | |
parent | 8c88bc5b489e785c7ead94ce6fc3adb7f76e8715 (diff) | |
download | linux-7beba04eb305393e3f8386390f25b4a9475f27f2.tar.xz |
kbuild: resolve symlinks for O= properly
Currently, Kbuild follows the logical chain of directories for the O=
option, just like 'cd' (or 'realpath --logical') does.
Example:
$ mkdir -p /tmp/a /tmp/x/y
$ ln -s /tmp/x/y /tmp/a/b
$ realpath /tmp/a/b/..
/tmp/x
$ realpath --logical /tmp/a/b/..
/tmp/a
$ make O=/tmp/a/b/.. defconfig
make[1]: Entering directory '/tmp/a'
[snip]
make[1]: Leaving directory '/tmp/a'
'make O=/tmp/a/b/.. defconfig' creates the kernel configuration in
/tmp/a instead of /tmp/x despite /tmp/a/b/.. resolves to /tmp/x.
This is because Kbuild internally uses the 'cd ... && pwd' for the
path resolution, but this behavior is not predictable for users.
Additionally, it is not consistent with how the Kbuild handles the
M= option or GNU Make works with 'make -C /tmp/a/b/..'.
Using the physical directory structure for the O= option seems more
reasonable.
The comment says "expand a shell special character '~'", but it has
already been expanded to the home directory in the command line.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <n.schier@avm.de>
Diffstat (limited to 'drivers/leds/Kconfig')
0 files changed, 0 insertions, 0 deletions