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



Hi Daniel,
On Sun, Jan 17, 2010 at 08:59:43AM -0500, Daniel Jacobowitz wrote:
> 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...

Yep... well sadly CodeSourcery only provide toolchains for the following
environments:

	i686-pc-linux-gnu
	i686-pc-mingw32

My environment is:
	mipsel-unknown-linux-gnu

and my computer will tell me where to go if I try to execute one of the
above i686-* environments on my computer.  (The dreadded "cannot execute
binary file" error.)  Hence my reasoning for rolling my own.

> 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.

Okay, I'll have a closer look.  I thought I had copied all the
environment variables out, but it's possible that I missed something --
the way the build script is written does not make it easy to follow.

Thanks for the heads-up.

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)      .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

I haven't lost my mind...
  ...it's backed up on a tape somewhere.