[Buildroot] Analysis of build failures
thomas.petazzoni at free-electrons.com
Sun Sep 7 07:41:45 UTC 2014
Dear Nathaniel Roach,
On Sun, 07 Sep 2014 11:49:18 +0800, Nathaniel Roach wrote:
> I don't have it installed purely because this chroot is *just* for the
> I'm leaning towards host-ncurses because it seems to be the cleaner way
> to do it, but assuming that the host has it installed is probably a
> fairly safe assumption.
> Only issue is that some people might have a build server they upload the
> config to, but even then installing ncurses-dev shouldn't really be a
> big deal.
See the discussion going with Peter, and the decision we need to take
> The offending tarballs have been moved out. I've checked them with file,
> gzip and even opened them in file-roller and I can't see an issue. They
> are up at http://nroach44.info/misc/br/ if you want to take a look.
> I have a suspicion that they may have been redownloaded, but I'm not
> sure if buildroot does wget -c or similar size checking logic by default.
We don't do size checking nor 'wget -c'. However, the autobuild-run
script deletes 5 random tarballs at the end of each build, in order to
make sure we regularly re-download the upstream tarballs. This is a way
to detect no longer available upstream sites, tarballs that have
changed and other similar things. Maybe you were lucky and the two
offending tarballs had been deleted and re-downloaded?
I guess we'll see over time what happens. Thanks for checking!
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
More information about the buildroot