crt0.o from newlib has ARM32-only routines when building gcc for arm-eabi
Tue Jun 19 17:06:00 GMT 2012
On Tue, Jun 19, 2012 at 3:17 PM, Khem Raj <firstname.lastname@example.org> wrote:
> On Tue, Jun 19, 2012 at 6:15 AM, David Fernandez
> <email@example.com> wrote:
>> unimplemented: Thumb-1 hard-float VFP ABI
That was the problem! (no need to add --disable-decimal-float, which
is disabled by default on arm targets). Thanks very much!
I guess this poses a few questions:
Should there be several crt0.o files available, that gcc should pick
depending on the -mthumb, -march, and -mcpu?
Is it that gcc is not quite there yet, or that newlib is not yet
compatible enough with the gcc multilib build system?
Any gcc guru knows something about this? As otherwise, the --target
configuration option does not produce a compiler supporting all the
cpus and architectures that the target covers in theory, and then
perhaps there should be a default prefix/suffix for the executables
and folders depending on the --with-cpu and/or --with-arch...
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc