Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder news
Date: Sat, 10 May 2014 22:28:27 +0200	[thread overview]
Message-ID: <536E8BEB.7020300@mind.be> (raw)
In-Reply-To: <20140504223611.5a6177c1@skate>

On 04/05/14 22:36, Thomas Petazzoni wrote:
> Hello,
> 
> Two news about the autobuilders:
> 
>  * The Crosstool-NG external toolchain configurations have been updated
>    and slightly extended. Yann E. Morin has provided me with a good set
>    of more up-to-date toolchains generated by Crosstool-NG, and I've
>    added them to the Free Electrons autobuilders, as a replacement for
>    the old ones. The new configurations are:
> 
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv5-ctng-linux-gnueabi.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv6-ctng-linux-uclibcgnueabi.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv7-ctng-linux-gnueabihf.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/i486-ctng-linux-uclibc.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/i686-ctng-linux-gnu.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/mips64el-ctng_n32-linux-gnu.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/mips64el-ctng_n64-linux-gnu.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/mipsel-ctng-linux-uclibc.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/powerpc-ctng_e500v2-linux-gnuspe.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/powerpc-ctng-linux-uclibc.config
>      http://autobuild.buildroot.org/toolchains/configs/free-electrons/x86_64-ctng_locales-linux-gnu.config

 Hi Thomas,

 Is it possible that you installed new binaries with the same name but a
different ctng configuration? That's a bit annoying because it breaks
reproducibility... It's OK to remove the old toolchains, but it would be good if
the new ones would have a different name.

 Regards,
 Arnout

> 
>  * As stated in another e-mail, the Free Electrons autobuilder
>    machine has been updated. It has twice the amount of RAM it used
>    to have (16 GB replaced by 32 GB), and a better storage system (SAS
>    10k disks instead of regular disks). Hopefully this should allow to
>    have more configurations tested every day.
> 
> Best regards,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-05-10 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 20:36 [Buildroot] Autobuilder news Thomas Petazzoni
2014-05-04 21:32 ` Luca Ceresoli
2014-05-10 20:28 ` Arnout Vandecappelle [this message]
2014-05-11 16:07   ` Thomas Petazzoni
2014-05-11 16:29   ` Thomas Petazzoni
2014-05-11 20:37     ` Arnout Vandecappelle
2014-05-11 21:14       ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2014-08-29 21:26 Thomas Petazzoni

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=536E8BEB.7020300@mind.be \
    --to=arnout@mind.be \
    --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