Re: [arm-gnu] Building arm-{none,stellaris}-eabi toolchains
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [arm-gnu] Building arm-{none,stellaris}-eabi toolchains



On Sun, Jan 17, 2010 at 08:51:37AM +1000, Stuart Longland wrote:
> /usr/local/lib/gcc/arm-stellaris-eabi/4.4.1/../../../../arm-stellaris-eabi/bin/ld:
> section .eh_frame loaded at [00014a70,00016c57] overlaps section .data
> loaded at [00014a70,00014bc3]

Obviously we don't support rebuilding our toolchains from source, and
prefer that people don't do so.  That out of the way...

There's a workaround in 2009q3 for a bug that will be fixed in our
next release.  It sets a gcc_cv_* cache variable in the environment;
you should be able to find it in the build script.  That will fix the
.eh_frame problem, which is GCC PR 40521.  Or just use
-fno-dwarf2-cfi-asm for now.

> 	Also worth pointing out, I've tried some of the others (Yagarto,
> GNUARM, etc.) which use an arm-elf target... these don't seem to work
> either, erroring out with binary compatibility errors (different FPU
> instruction sets, Thumb vs native ARM...etc).  Reading up seems to
> suggest I should be using EABI (arm-*-eabi), not the old ABI
> (arm-*-elf).  Or am I mistaken?

You are correct.  I highly discourage using arm-elf for anything
if you can avoid it.

-- 
Daniel Jacobowitz
CodeSourcery