From: Michal Marek <mmarek@suse.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v2] Kbuild: tiny correction on `make help`
Date: Wed, 14 Jun 2017 09:32:22 +0200 [thread overview]
Message-ID: <98403870-3c74-0730-2ffa-3048ed3827ad@suse.com> (raw)
In-Reply-To: <5940E10A.10309@cn.fujitsu.com>
Dne 14.6.2017 v 09:08 Cao jin napsal(a):
>
>
> On 06/14/2017 09:15 AM, Masahiro Yamada wrote:
>> 2017-06-13 18:52 GMT+09:00 Cao jin <caoj.fnst@cn.fujitsu.com>:
>>> Yamada-san,
>>>
>>> I have a question on the current top level Makefile. There are
>>> following lines, I have trouble to understand "firstword x$(MAKEFLAGS)"
>>> in 2nd line, why there is a 'x' there?
>>>
>>>
>>> ifneq ($(filter 4.%,$(MAKE_VERSION)),) # make-4
>>> ifneq ($(filter %s ,$(firstword x$(MAKEFLAGS))),)
>>
>>
>> I do not understand the 'x' either.
>>
>> Michal suggested the code according to the following:
>> https://patchwork.kernel.org/patch/3291301/
>> (I hope Michal can help you.)
>>
>
> It does helps.
>
>>
>> My first guess was, it was added just in case $(MAKEFLAGS) is empty.
>> Actually $(firstword ) seems to work with empty argument, though.
>>
>
> I see, I guess you are saying it was added in case there is no
> single-letter flags in $(MAKEFLAGS) while it has "--debug=jobs", that
> make sense to me. Thanks very much, Yamada-san.
Well, it more than three years ago. But yes, I believe that was the
intention:
make --foo=s
x$(MAKEFLAGS) => x --foo=s
$(firstword x$(MAKEFLAGS)) => x
Michal
prev parent reply other threads:[~2017-06-14 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 9:07 Cao jin
2017-06-06 15:01 ` Masahiro Yamada
2017-06-13 9:52 ` Cao jin
2017-06-14 1:15 ` Masahiro Yamada
2017-06-14 7:08 ` Cao jin
2017-06-14 7:32 ` Michal Marek [this message]
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=98403870-3c74-0730-2ffa-3048ed3827ad@suse.com \
--to=mmarek@suse.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®