Comment # 25 on bug 936463 from Stefan Br�ns

(In reply to Richard Biener from comment #21)
> 
> As it works for me with some targets isn't it only a disconnect between the
> binutils and cross-gcc target triplets?  There must be some configure magic
> to tell GCC not only about the build tools to use but about the tools to use
> in the installed system.  --with-as/--with-ld might work here I guess?
> I really don't like the extra symlinks.
> 
> Or we want to forgo with the idea to have multiple cross toolchains for the
> "same" target (like armv6hl and armv7hl as they just differ in their
> set of default target options).  Or we stop producing just a single
> cross-binutils package for them.

I also strongly prefer to have just one compiler for arm. Rationale:

1. cross-armv6hl-gcc and cross-armv7hl-gcc are essentially identical
  * same set of possible targets
  * both have "--with-float=hard"
2. everyone else uses an arm-<foo>-gnueabi triplet

Only minor downside is a little bit of convenience, as one builds by default
for the instruction set of the RPi1, the other one for everything else.