All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] build: specify minimum versions of make and binutils
Date: Tue, 19 Jan 2016 13:24:06 -0600	[thread overview]
Message-ID: <569E8D56.7030502@cardoe.com> (raw)
In-Reply-To: <569E065E02000078000C8596@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 2039 bytes --]

On 1/19/16 2:48 AM, Jan Beulich wrote:
>>>> On 18.01.16 at 18:21, <cardoe@cardoe.com> wrote:
>> On 1/18/16 11:03 AM, Jan Beulich wrote:
>>>>>> On 18.01.16 at 17:53, <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.html 
>>>> as 2.17. Knowing that Jan got these versions from SLES10 I looked up the
>>>> version of GNU make from the same vintage (mid-2006) and landed on 3.81.
>>>
>>> I'm afraid that same SLE10 has been using binutils 2.16.9<n>.<something>
>>> and make 3.80. While (still building Xen there once in a while) I'd probably
>>> not be in big trouble if we decided we don't want to support that old an
>>> environment anymore, I don't think we can just go and document higher
>>> versions than we so far allowed. We'd first need to settle on where to
>>> draw the line nowadays (which then likely would mean a gcc minimal
>>> version bum too).
>>
>> Not a problem. I was just trying to take the situation from a guessing
>> game to be explicitly called out. I was documenting what my logic was
>> behind the version numbers I selected. I wasn't able to compare dates
>> with binutils because their repo goes from 2003 to 2011 [1]. So I went
>> back to SLES10's release date [2] and the GCC 4.1.0 release date [3] to
>> compare it with GNU make [4].
>>
>> Honestly I'd be happy if we just drew a line in the sand so that its
>> clear what I need to test against when I submit patches. I don't really
>> care where the line is.
> 
> Then how about 2.16.1 and 3.80 respectively as the initial line?
> 
> Jan
> 

Sounds great to me. Would you like me to resubmit or do you want to make
that change. I'm ok if you throw away my patch and author it yourself.
Whatever is easiest for you (or whoever commits it).

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-19 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 16:53 [PATCH] build: specify minimum versions of make and binutils Doug Goldstein
2016-01-18 17:03 ` Jan Beulich
2016-01-18 17:21   ` Doug Goldstein
2016-01-19  8:48     ` Jan Beulich
2016-01-19 19:24       ` Doug Goldstein [this message]
2016-01-20  8:09         ` 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=569E8D56.7030502@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.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.