Rockbox mail archive
Subject: Re: ColdFire-rockbox and GCC 4.2.1
Re: ColdFire-rockbox and GCC 4.2.1
> The linker in binutils 2.17+ is picky about the CPU architecture (e.g.,
> whether it has a normal or enhanced MAC); it must match in all object
> files. But GCC's knowledge about them is very limited, so the
> GCC-specific libraries are only made for the architectures GCC knows
> about. That does not include the one for 5249, used when building Rockbox.
> > The X5 build gives has lots of undefined symbols (in addition to the
> > errors):
> Don't know what they are caused by though...
> > So it seems that I have gone wrong when trying to resolve problems.
> > If someone has any ideas (in addition to installing gcc-3.4 and
> > binutils-2.17), I'm very eager to read them. Thanks in advance!
> Use binutils 2.16 with GCC 4.2.1. It should fix the link problems at
> least. No good solution for screens.c though. However, in terms of code
> size and speed of the generated code, you might want to stick to GCC
> 3.4.6 (and perhaps my multiply patch :) for the time being.
> I built the latest gcc 4.3.0 and binutils 2.18+ snapshots yesterday and
successfully built rockbox for the iriver h300 with that, some small changes
to rockbox code were necessary though. If you just want to build rockbox I
recommend the recommeded combination of gcc 3.4.6 (possibly with lear's
patch) and binutils 2.16.1, but if you want to experiment with compilers I
think gcc 4.3 is more fun :-) If you are interested in my patches I will
post them somewhere for you.
Received on 2007-09-25
Page was last modified "Jan 10 2012" The Rockbox Crew