Talk:Bering-uClibc 5.x - Developer Guide - Adding a Hardware Architecture Variant

GNU_TARGET_NAME Setting

It's not clear to me how critical the value of GNU_TARGET_NAME is. Is "armv6-unknown-linux-uclibc" the right value or should we be using "armv6-unknown-linux-gnueabi" or something different again? Looking at e.g. source/$GNU_TARGET_NAME/toolchain/binutils-2.21.1/configure I'm seeing checks for target names like "arm*-*-linux-gnueabi" whereas none of the checks match a "-uclibc" suffix. Davidmbrooke 18:05, 27 March 2012 (UTC)

It's clear now - this is quite critical! Unless GNU_TARGET_NAME includes the string "gnueabi" then the GNU utilities (including GCC) will be configured for the old ARM OABI rather than for the EABI (which is what we want - especially if we state that the kernel will be compiled to use EABI (CONFIG_AEABI)). More info here.

On that basis it seems that "armv6-unknown-linux-uclibcgnueabi" is a good choice. Davidmbrooke 19:05, 31 March 2012 (UTC)