From: Emil Medve <Emilian.Medve@Freescale.com>
To: Michal Marek <mmarek@suse.cz>, <linux-kbuild@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: Fix silent builds with make-4
Date: Fri, 3 Jan 2014 10:18:49 -0600 [thread overview]
Message-ID: <52C6E2E9.6000309@Freescale.com> (raw)
In-Reply-To: <52C6DEE0.20600@suse.cz>
Hello Michal,
On 01/03/2014 10:01 AM, Michal Marek wrote:
> On 2013-12-05 22:56, Emil Medve wrote:
>> make-4 changed the way/order it presents the command line options
>> into MAKEFLAGS
>>
>> In make-3.8x, '-s' would always be first into a group of options
>> with the '-'/hyphen removed
>>
>> $ make -p -s 2>/dev/null | grep ^MAKEFLAGS
>> MAKEFLAGS = sp
>>
>> In make-4, '-s' seems to always be last into a group of options
>> with the '-'/hyphen removed
>>
>> $ make -s -p 2>/dev/null | grep ^MAKEFLAGS
>> MAKEFLAGS = ps
>>
>> Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
>> ---
>> Makefile | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Makefile b/Makefile
>> index 2c88e44..0332949 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -311,9 +311,15 @@ endif
>> # If the user is running make -s (silent mode), suppress echoing of
>> # commands
>>
>> +ifneq ($(filter 4.%,$(MAKE_VERSION)),) # make-4
>> +ifneq ($(filter %s -s%,$(MAKEFLAGS)),)
>
> The -s% here is unnecessary for two reasons: as you say, s is always at
> the end with make 4, and even if a long option is used, the hyphen is
> omitted:
>
> 3.82:
> $ make -s -p --no-print-directory | grep MAKEFLAGS
> MAKEFLAGS = --no-print-directory -sp
I was wondering how to account for the '-s%' pattern so I just preserved
it for make-4
> $ ./make/make -s -p --no-print-directory | grep MAKEFLAGS
> GNUMAKEFLAGS :=
> MAKEFLAGS = ps --no-print-directory
>
> And according to
> http://git.savannah.gnu.org/cgit/make.git/commit/?id=a674abe702cc0c017209a3186c32df050ff21f41,
> the space character is always there, even if there are no single-letter
> options. So we can do something like
>
> ifneq ($(filter %s ,$(firstword x$(MAKEFLAGS))),)
>
> and avoid accidentally matching things like --debug=jobs. Does the above
> work for you?
That's fine. I'll resubmit
Cheers,
prev parent reply other threads:[~2014-01-03 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:56 [PATCH] kbuild: Fix silent builds with make-4 Emil Medve
2014-01-03 16:01 ` Michal Marek
2014-01-03 16:18 ` Emil Medve [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=52C6E2E9.6000309@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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