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",
>
On Wed, May 8, 2013 at 6:14 PM, gnubie gnubie wrote:
> 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
> MULT
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:
./
