From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] Kbuild: fix # escaping in .cmd files for future Make
Date: Tue, 10 Jul 2018 16:09:21 +0200 [thread overview]
Message-ID: <20180710140921.GK1123@kroah.com> (raw)
In-Reply-To: <75b4a60a-e5f1-0f60-e4ac-a086d313b842@molgen.mpg.de>
On Thu, Jun 28, 2018 at 06:52:55PM +0200, Paul Menzel wrote:
> Dear Greg,
>
>
> On 06/28/18 01:51, Greg KH wrote:
> > On Wed, Jun 27, 2018 at 03:10:00PM +0200, Paul Menzel wrote:
> >> From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> >> Date: Sun, 8 Apr 2018 23:35:28 +0200
> >>
> >> commit 9564a8cf422d7b58f6e857e3546d346fa970191e upstream.
> >>
> >> I tried building using a freshly built Make (4.2.1-69-g8a731d1), but
> >> already the objtool build broke with
> >>
> >> orc_dump.c: In function ‘orc_dump’:
> >> orc_dump.c:106:2: error: ‘elf_getshnum’ is deprecated [-Werror=deprecated-declarations]
> >> if (elf_getshdrnum(elf, &nr_sections)) {
> >>
> >> Turns out that with that new Make, the backslash was not removed, so cpp
> >> didn't see a #include directive, grep found nothing, and
> >> -DLIBELF_USE_DEPRECATED was wrongly put in CFLAGS.
> >>
> >> Now, that new Make behaviour is documented in their NEWS file:
> >>
> >> * WARNING: Backward-incompatibility!
> >> Number signs (#) appearing inside a macro reference or function invocation
> >> no longer introduce comments and should not be escaped with backslashes:
> >> thus a call such as:
> >> foo := $(shell echo '#')
> >> is legal. Previously the number sign needed to be escaped, for example:
> >> foo := $(shell echo '\#')
> >> Now this latter will resolve to "\#". If you want to write makefiles
> >> portable to both versions, assign the number sign to a variable:
> >> C := \#
> >> foo := $(shell echo '$C')
> >> This was claimed to be fixed in 3.81, but wasn't, for some reason.
> >> To detect this change search for 'nocomment' in the .FEATURES variable.
> >>
> >> This also fixes up the two make-cmd instances to replace # with $(pound)
> >> rather than with \#. There might very well be other places that need
> >> similar fixup in preparation for whatever future Make release contains
> >> the above change, but at least this builds an x86_64 defconfig with the
> >> new make.
> >>
> >> Link: https://bugzilla.kernel.org/show_bug.cgi?id=197847
> >> Cc: Randy Dunlap <rdunlap@infradead.org>
> >> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> >> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
> >> ---
> >>
> >> Fix one conflict in `scripts/Kbuild.include`.
> >
> > What stable kernel(s) are you wanting this applied to?
>
> I tested, that it’s needed for 4.9 and 4.14. Strangely, it’s still not
> enough. I need the additional attached patch to be able to build the
> attached configuration with the stable series, while on master commit
> 9564a8cf (Kbuild: fix # escaping in .cmd files for future Make) seems
> to be enough, despite the same lines being present in
> `tools/build/Build.include`.
That's a crazy thing for make to do, ugh, tools should know better...
Anyway, both of these are now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2018-07-10 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 13:10 [PATCH] Kbuild: fix # escaping in .cmd files for future Make Paul Menzel
2018-06-27 23:51 ` Greg KH
2018-06-28 16:52 ` Paul Menzel
2018-07-10 14:09 ` Greg KH [this message]
2018-07-10 14:17 ` Paul Menzel
2018-07-10 14:25 ` Greg KH
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=20180710140921.GK1123@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.