xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	KeirFraser <keir@xen.org>, Doug Goldstein <cardoe@cardoe.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2] build: specify minimum versions of make and binutils
Date: Thu, 11 Feb 2016 10:59:57 +0000	[thread overview]
Message-ID: <1455188397.814.36.camel@citrix.com> (raw)
In-Reply-To: <56BC73AC02000078000D0EE6@prv-mh.provo.novell.com>

On Thu, 2016-02-11 at 03:42 -0700, Jan Beulich wrote:
> I think it is quite relevant which version is to be picked: Anything
> older no-one could legitimately report issues against (and I would
> very much like to continue to be able to submit build fixes I find
> necessary on those two old boxes I keep for a reason), while
> stating something too old which even today we don't successfully
> build with would be pretty odd.

So lets start with, for x86 whatever the older of the versions on the two
boxes you refer to above and for ARM gcc 4.8 and binutils 2.24, which
corresponds to what I happen to use for both arm32 and arm64 in my
development environment.

Those are IMHO reasonable starting points but obviously they aren't set in
stone and can be easily adjusted later if necessary.

Ian.

  reply	other threads:[~2016-02-11 10:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 23:12 [PATCH v2] build: specify minimum versions of make and binutils Doug Goldstein
2016-01-28 12:49 ` Jan Beulich
2016-01-28 13:02   ` Ian Campbell
2016-01-28 13:47     ` Jan Beulich
2016-01-28 14:39       ` Doug Goldstein
2016-02-10 20:36       ` Andrew Cooper
2016-02-11 10:42         ` Jan Beulich
2016-02-11 10:59           ` Ian Campbell [this message]
2016-02-11 11:21             ` Jan Beulich

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=1455188397.814.36.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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).