public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Sergei Trofimovich <slyich@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Makefules: fix MAKEFLAGS assignment for upcoming make-4.4
Date: Mon, 12 Sep 2022 16:27:25 -0400	[thread overview]
Message-ID: <b36fd227-a84d-32a4-5306-a0b288e64950@gotplt.org> (raw)
In-Reply-To: <20220909115039.3802300-1-slyich@gmail.com>



On 2022-09-09 07:50, Sergei Trofimovich via Libc-alpha wrote:
> make-4.4 will add long flags to MAKEFLAGS variable:
> 
>      * WARNING: Backward-incompatibility!
>        Previously only simple (one-letter) options were added to the MAKEFLAGS
>        variable that was visible while parsing makefiles.  Now, all options
>        are available in MAKEFLAGS.
> 
> This causes locale builds to fail when long options are used:
> 
>      $ make --shuffle
>      ...
>      make  -C localedata install-locales
>      make: invalid shuffle mode: '1662724426r'
> 
> The change fixes it by passing eash option via whitespace and dashes.
> That way option is appended to both single-word form and whitespace
> separated form.
> 
> Signed-off-by: Sergei Trofimovich <slyich@gmail.com>
> ---

Thanks, that's the right direction IMO but allowing word form flags will 
break this check too:

     ifeq    "$(findstring s,$(MAKEFLAGS))" ""       # if not -s

which is present in Makerules, Makeconfig and elf/rtld-Rules since the s 
will also match, e.g. --shuffle.  Those checks need to be fixed too.

Thanks,
Siddhesh

  reply	other threads:[~2022-09-12 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 11:50 Sergei Trofimovich
2022-09-12 20:27 ` Siddhesh Poyarekar [this message]
2022-09-12 21:27   ` [PATCH v2] Makerules: fix MAKEFLAGS assignment for upcoming make-4.4 [BZ# 29564] Sergei Trofimovich
2022-09-12 22:47     ` Paul Smith
2022-09-12 23:07       ` [PATCH v3] " Sergei Trofimovich
2022-09-13 14:21         ` Siddhesh Poyarekar

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=b36fd227-a84d-32a4-5306-a0b288e64950@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=libc-alpha@sourceware.org \
    --cc=slyich@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).