From: Ian Campbell <ian.campbell@citrix.com>
To: jbeulich@suse.com, andrew.cooper3@citrix.com,
xen-devel@lists.xen.org, stefano.stabellini@eu.citrix.com
Cc: Doug Goldstein <cardoe@cardoe.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH v3 2/2] build: specify minimum versions of make
Date: Thu, 11 Feb 2016 12:23:42 +0000 [thread overview]
Message-ID: <1455193422-14558-2-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1455193422-14558-1-git-send-email-ian.campbell@citrix.com>
From: Doug Goldstein <cardoe@cardoe.com>
To help people avoid having to figure out what versions of make
needs to be supported document it explicitly.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
v3: [ijc] Put make into a separate patch to reduce risk to
gcc+binutils patch #1 (since I'm not sure if v3.80 was really agreed)
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 356a350..dd36ec8 100644
--- a/README
+++ b/README
@@ -38,7 +38,7 @@ provided by your OS distributor:
* GCC
- For x86 4.1.2_20070115 or later
- For ARM 4.8 or later
- * GNU Make
+ * GNU Make v3.80 or later
* GNU Binutils:
- For x86 2.16.91.0.5 or later
- For ARM 2.24 or later
--
2.1.4
next prev parent reply other threads:[~2016-02-11 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 12:23 [PATCH v3 1/2] build: specify minimum versions of gcc and binutils Ian Campbell
2016-02-11 12:23 ` Ian Campbell [this message]
2016-02-11 12:30 ` [PATCH v3 2/2] build: specify minimum versions of make Andrew Cooper
2016-02-11 12:31 ` [PATCH v3 1/2] build: specify minimum versions of gcc and binutils Andrew Cooper
2016-02-11 13:21 ` Ian Campbell
2016-02-11 13:32 ` Jan Beulich
2016-02-11 15:38 ` Ian Campbell
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=1455193422-14558-2-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=jbeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 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 NNTP newsgroup(s).