From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tcmode-default: Set gcc 5.2 as the default
Date: Fri, 4 Sep 2015 17:47:50 +0200 [thread overview]
Message-ID: <20150904154750.GC2457@jama> (raw)
In-Reply-To: <1441380800.24871.173.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Fri, Sep 04, 2015 at 04:33:20PM +0100, Richard Purdie wrote:
> On Fri, 2015-09-04 at 08:29 -0700, Khem Raj wrote:
> > > On Sep 4, 2015, at 8:27 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > -GCCVERSION ?= "4.9%"
> > > +GCCVERSION ?= "5.2%"
> >
> > a small nit. Make it 5.% to logically indicate that 5.x is a bug fix release and next big upgrade will be
> > 6.x
>
> I'm not sure this would be a good idea. We have had 4.8 alongside 4.9
> and can imagine doing something like that with newer 5.x releases
> depending on how they work out. I doubt 5.2% hurts anything, apart from
> needing to tweak that file slightly more often...
But that was before GCC changed versioning scheme in 5, see
"Version Numbering Scheme for GCC 5 and Up" section in
https://gcc.gnu.org/develop.html
Having 5.1 alongside 5.2 isn't the same as 4.8 alongside 4.9 was.
I agree with Khem.
Ross: I agree that even small point release has to be tested, but this
variable is useful only to have multiple versions alongside each other,
which shouldn't be the case for 5.1 and 5.2 (or even 5.2.0 and 5.2.1 in
your example).
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-09-04 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 15:27 [PATCH] tcmode-default: Set gcc 5.2 as the default Richard Purdie
2015-09-04 15:29 ` Khem Raj
2015-09-04 15:32 ` Burton, Ross
2015-09-04 15:59 ` Khem Raj
2015-09-04 15:33 ` Richard Purdie
2015-09-04 15:47 ` Martin Jansa [this message]
2015-09-04 16:02 ` Khem Raj
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=20150904154750.GC2457@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.