Re: [Balloon] Building CUED images

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

No .config file in the equivalent directory in my build.

> Clues welcome, before I delve into the runes (still being somewhat
> unfamiliar with the new config system). Where should that config file
> be coming from?

Maybe it is a marker added later, it shouldn't exist at the start
AFAICT.

Incomplete clean?

Attach your complete .config ?

--


Neil Williams
=============
http://www.linux.codehelp.co.uk/