[Openembedded-users] Using a specific toolchain for a package when building a console-image

[Ville Seppänen]

Hi,

I need to build console-image with U-boot 1.3.4 for an ARM9 board. 
Unfortunately building that version of U-boot with the same toolchain as 
the rest of the image causes an error: "arm-angstrom-linux-gnueabi-ld: 
ERROR: Source object 
.../build/tmp/cross/arm/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/libgcc.a(_udivdi3.o) 
has EABI version 4, but target u-boot has EABI version 0". I googled a 
bit and found out 
(http://www.codesourcery.com/archives/arm-gnu/msg02332.html) that U-boot 
should not be built with arm-linux-gnueabi- but with arm-linux- instead. 
I've managed to tell bitbake this in my u-boot recipe, but this gives an 
error: "arm-linux-gcc not found" obviously because bitbake has not built 
this second toolchain.

How can I get bitbake to build a second toolchain to be used for U-boot, 
and rest of the image built with the original toolchain? Alternatively, 
is there a way to avoid this version mismatch error? I specifically need 
to use U-boot version 1.3.4 because I have been supplied a patch for 
that version.

Best Regards,
Ville Seppänen