Forcing symbol resolution in lib rather than bin

Jonathon McKitrick jcm at
Fri Aug 19 20:26:20 GMT 2005

On Fri, Aug 19, 2005 at 11:14:40PM +0300, Giorgos Keramidas wrote:
: On 2005-08-19 21:03, Jonathon McKitrick <jcm at> wrote:
: >On Fri, Aug 19, 2005 at 10:47:48PM +0300, Giorgos Keramidas wrote:
: >: # flame:/tmp/jcm-lib/foobar$ LD_LIBRARY_PATH=`pwd`/../libbar ./foobar
: >: # libfoo initialized at 0x80062a8a0
: >: # libbar initialized at 0x4004e4
: >: # flame:/tmp/jcm-lib/foobar$
: >
: > Hmmm.  I'm using my own makefile setup rather than the standard one.  I know
: > you're a big fan of <>  ;-)
: >
: > Doesn't ld *statically* link code from .a archives?
: 'statically' is such an overloaded term I prefer to avoid using it.
: The C linker will include the body of functions defined in non-shared
: libraries into every shared object that references them, AFAIK.  This is
: obvious if you run nm(1) on of the example above, because the
: libfoo_init() function is listed as 'T'.  I think that's what you want
: by making the libfoo.a library non-shared in the first place.

Got it!  I recalled something des or phk wrote me a while ago, then I skimmed
the manpage again.  I have to put the .a files AFTER the object files where
the unresolved symbol is found.

Jonathon McKitrick
Hoppiness is a good beer.

More information about the freebsd-questions mailing list