From: Ray Donnelly <mingw.android@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>, crossgcc@sourceware.org
Subject: [PATCH 1 of 1] Allow reordered MAKEFLAGS
Date: Wed, 10 Jul 2013 11:55:00 -0000 [thread overview]
Message-ID: <CAOYw7dsdsg-XaDOwwEWJeUUSo2Vu_UD5GtkSgNTu59ai7yx0cQ@mail.gmail.com> (raw)
# HG changeset patch
# User Ray Donnelly <mingw.android@gmail.com>
# Date 1373456421 -3600
# Wed Jul 10 12:40:21 2013 +0100
# Node ID 4972bd801ee6942dd1a27d4ffdd06f15482a7c45
# Parent 2685dfa9de14fbe356ba76cb201bf5c039cf6860
Allow reordered MAKEFLAGS
-R and -r (-Rr) can be reordered to -r and -R (-rR).
This happens with MSYS1/2 gnu-make and mingw32-make,
and triggers "Recursion detected, bailing out..."
Signed-off-by: Ray Donnelly <mingw.android@gmail.com>
diff -r 2685dfa9de14 -r 4972bd801ee6 Makefile.in
--- a/Makefile.in Thu May 23 17:51:15 2013 +0200
+++ b/Makefile.in Wed Jul 10 12:40:21 2013 +0100
@@ -24,9 +24,14 @@
# Note: dual test, because if -R and -r are given on the command line
# (who knows?), MAKEFLAGS contains 'Rr' instead of '-Rr', while adding
# '-Rr' to MAKEFLAGS adds it literaly ( and does not add 'Rr' )
+# Further: quad test because the flags 'rR' and '-rR' can be reordered.
ifeq ($(filter Rr,$(MAKEFLAGS)),)
ifeq ($(filter -Rr,$(MAKEFLAGS)),)
+ifeq ($(filter rR,$(MAKEFLAGS)),)
+ifeq ($(filter -rR,$(MAKEFLAGS)),)
CT_MAKEFLAGS += -Rr
+endif # No -rR
+endif # No rR
endif # No -Rr
endif # No Rr
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2013-07-10 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 11:55 Ray Donnelly [this message]
2013-07-15 21:06 ` Yann E. MORIN
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=CAOYw7dsdsg-XaDOwwEWJeUUSo2Vu_UD5GtkSgNTu59ai7yx0cQ@mail.gmail.com \
--to=mingw.android@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@free.fr \
/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).