Hi Terry,
Thank you very much. It was this macro that I had managed to miss:
> #ifndef MULTILIB_DEFAULTS
> #define MULTILIB_DEFAULTS \
> - { "marm", "mlittle-endian", "mfloat-abi=soft",
> "mno-thumb-interwork", "fno-leading-underscore" }
> + { "mthumb", "mlittle-endian", "mfloat-abi=soft",
>
Hi,
I've noticed odd behaviour when building an ARM compiler with GCC 4.7,
--with-mode=thumb and multilibs enabled.
If I do a standard c/c++ newlib build with the following multilib options:
MULTILIB_OPTIONS += marm mthumb
MULTILIB_DIRNAMES+= arm thumb
we get the following static libs:
./
Hi,
I notice that if you add a DRIVER_SELF_SPEC option and then add that
option as a MULTILIB_OPTION, it doesn't build certain libraries for
that multilib variant.
for example, if you add:
"%{mtestoption:-mcpu=cortex-a5 %
