From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder update
Date: Sun, 13 Mar 2016 13:08:15 +0100 [thread overview]
Message-ID: <20160313130815.002d7f15@free-electrons.com> (raw)
In-Reply-To: <20160312225838.GL3745@free.fr>
Hello,
On Sat, 12 Mar 2016 23:58:38 +0100, Yann E. MORIN wrote:
> > Some autobuilder updates:
> >
> > - All the Buildroot pre-built external toolchains have been rebuilt
> > with Buildroot 2016.02 + a few patches. To see which patches I'm
> > using to build those external toolchains, see the branch at:
> >
> > http://git.free-electrons.com/users/thomas-petazzoni/buildroot/log/?h=br-ext-toolchain-fixes
> >
> > - The br-sh4-full configuration has been changed to actually use the
> > Buildroot toolchain, and not the pre-built Musl-cross toolchain.
> >
> > - I've fixed the Free Electrons build server, which was no longer
> > building anything since quite some time, due to a lack of disk
> > space. This will help re-increase the number of builds done each day.
>
> I updated my instance yesterday evening. Thanks! :-)
In fact, updating your instance was not needed. The changes I made only
affect the .config files, which are re-downloaded every time a build
starts. So updating the autobuild-run script is not needed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-13 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 22:47 [Buildroot] Autobuilder update Thomas Petazzoni
2016-03-11 5:27 ` Bernd Kuhls
[not found] ` <E1aeFbm-0004jE-Q7@fli4l.lan.fli4l>
2016-03-11 8:42 ` Thomas Petazzoni
2016-03-11 10:57 ` Peter Korsgaard
2016-03-11 13:38 ` Thomas Petazzoni
2016-03-11 14:20 ` Peter Korsgaard
2016-03-11 11:08 ` Peter Korsgaard
2016-03-11 13:37 ` Thomas Petazzoni
2016-03-11 14:21 ` Peter Korsgaard
2016-03-12 22:58 ` Yann E. MORIN
2016-03-13 12:08 ` Thomas Petazzoni [this message]
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=20160313130815.002d7f15@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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