On 2016-01-21, Albert ARIBAUD wrote: > On Sat, 16 Jan 2016 12:21:06 +0100, Albert ARIBAUD > <albert.u.b...@aribaud.net> wrote: >> On Fri, 15 Jan 2016 15:30:47 -0800, Martin Michlmayr <t...@cyrius.com> wrote: >> > * Albert ARIBAUD <albert.u.b...@aribaud.net> [2016-01-15 22:52]: >> > You can find the build log here, btw: >> > https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=armel&ver=2016.01%2Bdfsg1-1&stamp=1452650663 >> >> Thanks. I see the build was done by newer gcc (5.3.1) and binutils >> (2.25.90). I will set up a local buildd so that I can reproduce this( >> and future builds an analyze them as needed). > > Hmm, installing a complete buildd instance seems overkill. Is there a > simple way to set up a build environment identical to that of the > buildd which created u-boot.kwb? I've got VMs with basic Jessie, > Testing and Unstable installs.
Are your virtual machines running armel? The builds in debian are native builds, so to really replicate the build environment, you'd need to run the builds natively as well. There are cross-toolchains available in Debian unstable/sid, though that won't be the exact build environment, of course. In any case, you'll need deb-src lines in your /etc/apt/sources.list* files, corresponding to each of the deb lines, such as: deb http://httpredir.debian.org/debian sid main deb-src http://httpredir.debian.org/debian sid main And then, to install the build toolchain: apt-get install build-essential fakeroot devscripts apt-get build-dep u-boot apt-get install crossbuild-essential-armel # if using cross-toolchains I do find sbuild + schroot to be my preferred build environment, which handles the steps above for most cases. Some people also use pbuilder or one of the pbuilder-based variants such as cowbuilder, which has similar functionality. Hope that helps; Thanks for testing! live well, vagrant
signature.asc
Description: PGP signature
