This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- From: "H. J. Lu" <hjl at lucon dot org>
- To: David Daney <ddaney at avtrex dot com>
- Cc: gcc at gcc dot gnu dot org, binutils at sources dot redhat dot com
- Date: Thu, 28 Jul 2005 13:37:29 -0700
- Subject: Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- References: <42E9368F.7000506@avtrex.com>
On Thu, Jul 28, 2005 at 12:48:31PM -0700, David Daney wrote:
> I am not sure if this is a GCC problem or a binutils problem.
>
> I have a a mipsel-linux cross compiler (gcc-3.4.3/binutils-2.16.1) and
> whenever I compile even the simplest hello-world.c libgcc_s.so is linked.
>
> When I do the same thing natively on my i686/FC3, libgcc_s.so is not linked.
>
> If if explicitly pass -static-libgcc to the cross compiler I do not need
> libgcc_s.so (as would be expected).
>
> As you can see from the transcript below libgcc_s is being linked with
> --as-needed.
>
> Also you can see that neither hello-world.o nor my libc-2.3.3.so have
> any undefined symbols that would be satisfied by libgcc_s.so.
>
> Any ideas about what is going on here?
>
Does your glibc need libgcc_s.so? Can you try the current binutils?
H.J.