compile u-boot without Angstrom

Hi!

Once I built Angstrom Linux using setup-scripts. Eventually I got
necessary sources for u-boot and kernel that I used for my needs. The
problem I have now is how to compile u-boot-2011.12-r3 without OE
toolchain. Trying to build u-boot with recommended CodeSourcery
arm-2009q1-203 I have the following troubles:

/opt/arm-2009q1/bin/arm-none-linux-gnueabi-ld: section .bss [8013dfa4
-> 8016ffeb] overlaps section .rel.dyn [8013dfa4 -> 80143e03]
/opt/arm-2009q1/bin/arm-none-linux-gnueabi-ld: section .dynsym
[80143e04 -> 80143ec3] overlaps section .bss [8013dfa4 -> 8016ffeb]
/opt/arm-2009q1/bin/arm-none-linux-gnueabi-ld: u-boot: section .bss
vma 0x8013dfa4 overlaps previous sections
make: *** [u-boot] Error 1

Building u-boot with native Angstrom gcc is fine. Unfortunately I have
to distribute sources to my client and they want to use CodeSourcery
toolchain without waiting for hours to build Angstrom at all PCs they
have. Is there any specific CodeSourcery version for this u-boot
revision or there are some tricks to avoid troubles?

Can you use the prebuilt toolchain for OE? It should work as well as
the self-compiled and you can easily add necessary devel packages, tar
the entire /usr/local/angstrom directory and deploy to the devel
machines.

j.

CodeSourcery 2010q1-202 works fine

Enable sstate mirrors or just hand them a prebuilt toolchain from angstrom. No need to subject them to the horrors of prebuilt codesourcery toolchains.

Koen,

is it possible just to tar the prebuilt toolchain from angstrom and
unpack it at another PC without the rest of OE environment? Should the
OE root directory structure be kept? I mean, for example:
1) was in OE: ~/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi
and keep this directories tree at a client's PC or:
2) just untar and place the toolchain into /opt directory?

please advise

Koen,

is it possible just to tar the prebuilt toolchain from angstrom and
unpack it at another PC without the rest of OE environment? Should the
OE root directory structure be kept? I mean, for example:
1) was in OE: ~/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi
and keep this directories tree at a client's PC or:
2) just untar and place the toolchain into /opt directory?

please advise

'bitbake meta-toolchain' and distribute that. That has more tweaks to be relocatable. There's a news article on the angstrom frontpage on how to use it.