From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Doug Goldstein <cardoe@cardoe.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2] build: specify minimum versions of make and binutils
Date: Thu, 28 Jan 2016 13:02:20 +0000 [thread overview]
Message-ID: <1453986140.26591.81.camel@citrix.com> (raw)
In-Reply-To: <56AA1C8502000078000CC01A@prv-mh.provo.novell.com>
On Thu, 2016-01-28 at 05:49 -0700, Jan Beulich wrote:
> > > > On 28.01.16 at 00:12, <cardoe@cardoe.com> wrote:
> > To help people avoid having to figure out what versions of make and
> > binutils need to be supported document them explicitly. The version of
> > binutils that had to be supported was mentioned in
> > http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg00609.ht
> > ml
> > as 2.17 recently. It was decided that the versions should instead be
> > GNU binutils 2.16.1 and GNU Make 3.80 in
> > http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg02134.ht
> > ml
>
> "decided" is a bit strong. I suggested these values. And while I'm
> pretty certain that even plain make 3.80 will work, I'm in no way
> sure plain 2.16.1 will (what I'm building with once in a while is some
> 2.16.9x, and I can't say how many backports it has). So the
> question really is - did you test that things build with these?
Why would he have done, you suggested 2.16.1 with no hint that you thought
it might not be a reasonable version to use.
TBH having rejected Doug's original proposal I would have said it was up to
you to specify the actual precise versions you think should be used, rather
than making Doug guess and leading him down blind allies by making
apparently authoritative suggestions which you secretly aren't actually
sure about yourself.
Anyway we could go round and round like this forever. What's wrong with
starting with this as a baseline and bumping it if it turns out to be a
problem in practice?
> Also I'm not sure 2.16.1 is going to be sufficient for ARM (it's
> most definitely too old for ARM64).
I suppose there is an implicit max(version, first version supporting arch).
I don't think we can really go into the level of detail needed for per arch
toolchain requirements.
I certainly don't know which version of either gcc or binutils is needed to
build either ARM variant.
Ian.
next prev parent reply other threads:[~2016-01-28 13:02 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 [this message]
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
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=1453986140.26591.81.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.