[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNARN_Ofzog5J1XWoW3dB6_m2wfVuFPYjvFkfdb0pnBR9gA@mail.gmail.com>
Date: Sat, 14 Oct 2017 12:17:01 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Cc: Joe Perches <joe@...ches.com>, Tom Rini <trini@...sulko.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Matthias Kaehlcke <mka@...omium.org>,
Cao jin <caoj.fnst@...fujitsu.com>,
Arnd Bergmann <arnd@...db.de>, James Hogan <jhogan@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jan-Simon Möller <dl9pf@....de>,
Michal Marek <michal.lkml@...kovi.net>,
Douglas Anderson <dianders@...omium.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Mark Charlebois <charlebm@...il.com>
Subject: Re: [PATCH 0/2] kbuild: use relative path from $(srctree) instead of __FILE__
2017-10-12 18:56 GMT+09:00 Masahiro Yamada <yamada.masahiro@...ionext.com>:
>
> Kbuild works in objtree, not in srctree. So, __FILE__ is prefixed
> with $(srctree)/ for out-of-tree build.
>
> For example, WARN_ON() will look as follows if you built your kernel
> out of source tree:
>
> WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:...
>
> With this series, it will always look like follows regardless of O= option.
>
> WARNING: CPU: 1 PID: 1 at arch/arm64/kernel/foo.c:...
>
> If GCC does not support -Wno-builtin-macro-redefined (i.e. gcc version < 4.4),
> the output is prefixed with absolute path.
>
I expect to replace __FILE__ with its relative path,
but actually it replaces __FILE__ with relative path of __BASE_FILE__.
This will change the behavior in several places.
I take back this series.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists