Re: [Balloon] Building CUED images

+++ Wookey [2012-06-10 15:55 +0100]:
> +++ Neil Williams [2012-06-06 08:04 +0100]:
> > On Wed, 6 Jun 2012 02:35:16 +0100
> > Wookey <wookey@wookware.org> wrote:
> >
> > > So I tried building trunk with defaults except setting
> > > BR2_VARIANT_CUED=y
> > > BR2_BUILDROOT_NOV_2011=y
> > > BR2_OPENOCD=y
> > > # BR2_ROOTFS_YCT is not set
> > >
> > > i.e we also have:
> > > BR2_KERNEL_2.6.37.6=y
> > > BR2_YAFFS_2011-02-09=y
> > >
> > > Should I expect this to work?
> >
> > I haven't done any CUED builds for ages, also haven't been doing stuff
> > in trunk/ for almost as long.
> >
> > However, I just tried a similar CUED build in trunk and
> > configBalloon3-CUED-2010.11 does not exist anywhere in my tree, so that
> > code doesn't get called.
> >

> > > if [ -f configBalloon3-CUED-2011.11 ]; then \
> > >         cp configBalloon3-CUED-2011.11 /home/wookey/projects/balloon/svn/trunk/build/buildroot/buildroot-2011.11/.config; \
> > >     else \
> > >         cp configBalloon3-2011.11 /home/wookey/projects/balloon/svn/trunk/build/buildroot/buildroot-2011.11/.config; \
> > >     fi;

> >
> > That logic looks, umm, borked. If file exists, copy it - else copy it
> > anyway? That else can't be being called.
> >
> > FTR it's the same code in the menuconfig2 branch which I am building
> > quite often recently, without problems.
> >
> > > cp: cannot create regular file `/home/wookey/projects/balloon/svn/trunk/build/buildroot/buildroot-2011.11/.config': No such file or directory
>
> OK, so the problem here is that
> /home/wookey/projects/balloon/svn/trunk/build/buildroot/buildroot-2011.11
> does not get created. Only
> /home/wookey/projects/balloon/svn/trunk/build/buildroot/buildroot-2010.11
> does, which seems wrong to me. The config seems to have downloaded the
> 2010.11 version of buildroot, and unpacked it, but then notices a bit
> later in the build that 2011.11 was configured and tries to use the
> config and dir for that. The config exists but the dir doesn't.

Turns out the reason for this is that we just stamp the 'buildroot
unpacked' event, not which one. So make notes that it's been done and
proceeds. It doesn't notice that the config has changed since last
time this was done.

So you only hit this issue if the build dir has old builds in it.

Clearing out build/buildroot and re-making sorts things out.

Now to see if anything actually works :-)

Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/