RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
James E Wilson
wilson@specifix.com
Thu Jul 28 21:26:00 GMT 2005
More information about the Binutils mailing list
Thu Jul 28 21:26:00 GMT 2005
- Previous message (by thread): RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- Next message (by thread): RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 built the optimal way, it is possible for crtbegin.o to have register_frame_info and deregister_frame_info calls for C++ EH unwinding which would require libgcc always. If built the optimal way, then the gcc/glibc toolchain will use an alternate method for C++ EH unwinding that does not require crtbegin.o support and hence does not require libgcc. This is why the x86 FC3 is OK. See the USE_PT_GNU_EH_FRAME stuff in gcc/crtstuff.c. -- Jim Wilson, GNU Tools Support, http://www.specifix.com
- Previous message (by thread): RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- Next message (by thread): RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list