Jeff Blaine <jblaine@xxxxxxxxx> writes: > Hi Ian, thanks for the reply. > > >> I didn't get an answer to my previous long post about the > >> problem I am having, so I figured I would try asking > >> more direct questions: > >> > >> What, in GCC, makes the determination to link in -lgcc? > > -lgcc is always linked in. > > I assume you are asking: what decides whether to link it statically > > or > > dynamically? That is controlled by the -static-libgcc and > > -shared-libgcc options, q.v. > > I forgot to mention this below -- I also tried LDFLAGS="-static-libgcc" > and watched it be referenced/used during my build. It did nothing. > The resulting build had libgcc_s.so linked. I have no explanation for this behaviour. If you run the link command using the -v option, does it pass -lgcc_s to the linker? Is there any chance that you somewhere have a file named libgcc.so? (You should normally have libgcc.a and libgcc_s.so). Ian
