Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread Richard Sandiford
David Daney <[EMAIL PROTECTED]> writes: > 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. FWIW, I'm seeing the same thing with a similar native setup. I hope to have a look at it soon. Richard

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread David Daney
H. J. Lu wrote: On Thu, Jul 28, 2005 at 01:54:40PM -0700, David Daney wrote: Do you know of a patch to binutils since 2.16.1 that would fix the problem? I remember there were some patches for as needed. But I don't know if they are in 2.16.1 or not. HEAD also seems to fail. David Daney.

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread Mike Frysinger
On Thursday 28 July 2005 08:22 pm, James E Wilson wrote: > On Thu, 2005-07-28 at 16:58, Greg Schafer wrote: > > Glibc headers ARE provided -> inhibit_libc NOT defined -> optimal > > Glibc headers ARE NOT provided -> inhibit_libc IS defined -> suboptimal > > This is basically what I meant, but I d

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread H. J. Lu
On Thu, Jul 28, 2005 at 01:54:40PM -0700, David Daney wrote: > > Do you know of a patch to binutils since 2.16.1 that would fix the problem? > I remember there were some patches for as needed. But I don't know if they are in 2.16.1 or not. H.J.

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread James E Wilson
On Thu, 2005-07-28 at 16:58, Greg Schafer wrote: > Glibc headers ARE provided -> inhibit_libc NOT defined -> optimal > Glibc headers ARE NOT provided -> inhibit_libc IS defined -> suboptimal This is basically what I meant, but I don't want to get in a debate about what is optimal and what isn't

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread Greg Schafer
On Thu, Jul 28, 2005 at 02:26:16PM -0700, James E Wilson wrote: > It looks like you forgot to check the crt*.o files for undefined > references. > > If the gcc/glibc toolchain wasn't built the optimal way, it is possible > for crtbegin.o to have register_frame_info and deregister_frame_info > cal

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread Richard Henderson
On Thu, Jul 28, 2005 at 02:26:16PM -0700, James E Wilson wrote: > On Thu, 2005-07-28 at 12:48, David Daney wrote: > > 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. > > It looks like you forgot to check the c

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread James E Wilson
On Thu, 2005-07-28 at 12:48, David Daney wrote: > 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. It looks like you forgot to check the crt*.o files for undefined references. If the gcc/glibc toolchain wasn't b

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread David Daney
H. J. Lu wrote: 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

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread H. J. Lu
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 sa

RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...

2005-07-28 Thread David Daney
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 exp