tools-linking-owner at opensolaris.org wrote: > LD_DEBUG=-Dsymbols,reloc,detail /ws/onnv-tools-prc/SUNWspro/SS11/bin/cc > -DHAVE_CONFIG_H -I. -I.. -I.. -I../compat -i -g -xstrconst -xpentium > -mr -xregs=no%frameptr -mt -D__inline=inline -c event-test.c > LD_DEBUG=-Dsymbols,reloc,detail /ws/onnv-tools-prc/SUNWspro/SS11/bin/cc > -I.. -I../compat -i -g -xstrconst -xpentium -mr -xregs=no%frameptr -mt > -D__inline=inline -o event-test event-test.o ../.libs/libevent.a -lnsl > -lrt -lresolv -lsocket
BTW. There are two link-editors with debugging capabilities, ld.so.1(1) and ld(1). The environment variable LD_DEBUG=token is read and interpreted by ld.so.1(1). The command line argument -Dtoken is read by ld(1). However, when driven by the compiler driver, it's common to enable ld(1)'s debugging with the environment variable LD_OPTIONS=-Dtoken. The debugging output you sent showed the runtime bindings of the various components of the compilation - not the relocation processing carried out be ld(1). 09809: 1: transferring control: /ws/onnv-tools-prc/SUNWspro/SS11/prod/bin/cc ..... 09810: 1: transferring control: /ws/onnv-tools-prc/SUNWspro/SS11/prod/bin/acomp ..... 09811: 1: transferring control: /ws/onnv-tools-prc/SUNWspro/SS11/prod/bin/fbe ..... 09812: 1: transferring control: /usr/bin/mcs ..... 09812: 1: transferring control: /usr/bin/amd64/mcs ..... 09818: 1: transferring control: /ws/onnv-tools-prc/SUNWspro/SS11/prod/bin/cc ..... 09819: 1: transferring control: /usr/bin/ld :-) -- Rod.
