Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>,
	Yocto Discussion Mailing List <yocto@yoctoproject.org>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [RFT] gcc 6.2 RC1 update
Date: Fri, 19 Aug 2016 11:14:04 +0100	[thread overview]
Message-ID: <1471601644.16712.23.camel@linuxfoundation.org> (raw)
In-Reply-To: <888B09F3-F9A2-49C1-86E8-E33FA1FE6521@gmail.com>

On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote:
> Hi All
> 
> I have put together recipe upgrade for upcoming gcc 6.2 release now
> that it entered RC phase. With gcc 6.2 the recipes are using tarballs
> instead of git fetcher as promised :)
> Please help testing it out in your setups and report any issues you
> see.
> 
> The commit you need to cherry-pick for OE-core is this one
> 
> https://github.com/kraj/openembedded-core/commit/0319b603761a16e65d70
> 4336112c3709a8bf771c
> 
> Thank you for your help

I put this through the autobuilder and it passed so I've merged it. I
did this quickly as we're putting a "pre M3" build through a QA cycle
and I wanted to get some of the more invasive changes into that build
so we don't have a stampeding herd of patches breaking everything
coming up to the final feature freeze for 2.2.

In other news, we are now also testing musl world builds on the
autobuilder as part of regular testing.

Cheers,

Richard




  reply	other threads:[~2016-08-19 10:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 18:55 [RFT] gcc 6.2 RC1 update Khem Raj
2016-08-19 10:14 ` Richard Purdie [this message]
2016-08-19 13:40   ` Khem Raj
2016-08-19 14:04     ` Gary Thomas
2016-08-19 14:06       ` Gary Thomas
2016-08-19 14:59         ` Khem Raj
2016-08-19 15:05           ` Gary Thomas
2016-08-19 16:01             ` Khem Raj
2016-08-20 14:15               ` Gary Thomas

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=1471601644.16712.23.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=yocto@yoctoproject.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