From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>, Gary Thomas <gary@mlbassoc.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Future of GCC
Date: Tue, 12 Jul 2016 14:14:50 -0700 [thread overview]
Message-ID: <57855DCA.1080807@gmail.com> (raw)
In-Reply-To: <CAJTo0LbByAsem7asRmieaeVvLHarr8D9zynCUncEqt0J2JvmfQ@mail.gmail.com>
On 07/12/2016 01:15 AM, Burton, Ross wrote:
> On 12 July 2016 at 08:57, Gary Thomas <gary@mlbassoc.com> wrote:
>
>> Now that GCC 4.x is gone, we're left with (currently) 5.4 & 6.1
>> Is the intention to track these both for a while, or will 5.x
>> also be gone once things are working with 6.x?
>>
>> ... just wondering where to spend my effort since I'll have to
>> make my targets (some are very old) work with at least 5.x
>>
>> Any advice? Thanks
>>
>
> Personally I was thinking that gcc 5.x and 6.x should stay in oe-core for
> this cycle, and then drop 5.x after the release.
Wouldn't that be dropped iff GCC 7.0 is release? or are you saying we
should only have one GCC version?
- armin
I'm not the toolchain
> owner though so that's just an opinion.
>
> In theory bringing back toolchains isn't rocket science - just copying the
> 4.x recipes from oe-core prior to their removal into a new layer and
> setting GCCVERSION should work.
>
> Ross
>
>
>
next prev parent reply other threads:[~2016-07-12 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 7:57 Future of GCC Gary Thomas
2016-07-12 8:15 ` Burton, Ross
2016-07-12 21:14 ` akuster808 [this message]
2016-07-12 21:24 ` Burton, Ross
2016-07-12 21:34 ` akuster808
2016-07-12 22:27 ` Richard Purdie
2016-07-12 23:15 ` Khem Raj
2016-07-13 12:46 ` Martin Jansa
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=57855DCA.1080807@gmail.com \
--to=akuster808@gmail.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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