From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Update of pre-built Buildroot toolchains
Date: Thu, 22 Sep 2016 18:43:29 +0530 [thread overview]
Message-ID: <57E3D8F9.4020109@imgtec.com> (raw)
In-Reply-To: <20160921210722.1b078ab1@free-electrons.com>
Hi Thomas,
On Thursday 22 September 2016 12:37 AM, Thomas Petazzoni wrote:
> Hello,
>
> I have just deployed a new set of pre-build Buildroot toolchains in the
> autobuilders. The toolchains have all been rebuilt as of commit
> 589cbc61b0913891fd00019365e52b9e50ff7250. Major changes are:
>
> * Almost all toolchains have been switched to the default of gcc 5.x.
> There are still a few toolchains that intentionally use different
> gcc version: some using gcc 6.x, some using gcc 4.8.x.
>
> * The ARC toolchain has been updated with the latest version of the
> ARC toolchain components.
>
> * The Blackfin toolchain has the latest uClibc fix.
It looks like bfin config on autobuilder is not updated to use new
pre-build toolchain.
Regards,
Rahul
next prev parent reply other threads:[~2016-09-22 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 19:07 [Buildroot] Update of pre-built Buildroot toolchains Thomas Petazzoni
2016-09-22 13:13 ` Rahul Bedarkar [this message]
2016-10-17 15:02 ` Thomas Petazzoni
2016-09-24 18:04 ` Bernd Kuhls
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=57E3D8F9.4020109@imgtec.com \
--to=rahul.bedarkar@imgtec.com \
--cc=buildroot@busybox.net \
/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