Sat Jul 25 11:31:28 CEST 2009


Starting with Debian nomenclature, there are two different arm

   arm-linux-gnueabi-gcc  /usr/arm-linux-gnueabi
   arm-linux-gnu-gcc      /usr/arm-linux-gnu

The Montavista toolchain and more importantly, the closed source TI
object files use the former.  Doesn't look like there is a way around

The linux config side is confusing though.  Dumping the current config
(see [4]) I see:

# CONFIG_AEABI is not set

I'm not sure what that is about..  Linux uses the old ABI, and the
userland the new?

[1] http://wiki.debian.org/ArmEabiPort
[2] http://cateee.net/lkddb/web-lkddb/AEABI.html
[3] http://cateee.net/lkddb/web-lkddb/OABI_COMPAT.html
[4] entry://20090725-115612
[5] http://wiki.debian.org/ArmEabiHowto