This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: The absence of a arm-thumb interworking libgcc.a
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Rimpei Sosa <sosa dot rimpei at jp dot panasonic dot com>
- Cc: Richard dot Earnshaw at arm dot com, gcc at gcc dot gnu dot org
- Date: Fri, 06 Jun 2003 11:21:18 +0100
- Subject: Re: The absence of a arm-thumb interworking libgcc.a
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> > You need to uncomment the multi-lib options that build the interworking
> > variants of libgcc.a (they are in the same file as the ones you cite
> > above).
> >
> > # MULTILIB_OPTIONS += mno-thumb-interwork/mthumb-interwork
> > # MULTILIB_DIRNAMES += normal interwork
> > # MULTILIB_EXCEPTIONS += *mapcs-26/*mthumb-interwork*
> > #
> >
> > Having done that you will have to rebuild and install your compiler.
>
> Following your advice I fixed t-arm-elf and rebuilded gcc.
> But I don't see any changes have been made to gcc.
>
> I'm guessing t-arm-elf doesn't have any effect on building gcc
> when --target=arm-linux is specified at configuration ,whereas t-linux does.
> Am I right?
Yep.
>
> In order to produce a libgcc.a which support thumb interworking
> do I need to fix t-linux?
>
Yep. Whether or not a Linux system supports Thumb code in general though
is a separate issue that you also need to consider.
R.