topic GCC doesn't link libraries properly in Operating System - HP-UX

GCC doesn't link libraries properly

Kalin Evtimov — Mon, 04 Jul 2005 04:07:45 GMT

Hi!
I am compiling a program with gcc, but although I have a linker opition -lrrd, which should link to a librrd.so library, it doesn't. If I use chatr on the compiled file, I see:

64-bit ELF shared library
shared library dynamic path search:
LD_LIBRARY_PATH enabled first
SHLIB_PATH enabled second
embedded path enabled third -lrrd
shared library list:
libm.so.1
shared vtable support disabled

This library is not in the shared list!
Does anybody know why?

P.S. What does the +b option of gcc mean?

Thank you!

Re: GCC doesn't link libraries properly

Amit Agarwal_1 — Mon, 04 Jul 2005 04:30:32 GMT

It is not necessary that your application is actually dependent on libraries that you link with. You can specify any number of libraries at the link time, but linker will keep only those names which resolves any external refernces in application.

In your case, it seems that your application is not calling any procedure/function defined in librrd.so. Hence it is not shown in the chatr output.

-Amit

Re: GCC doesn't link libraries properly

Kalin Evtimov — Mon, 04 Jul 2005 04:35:43 GMT

But this librray is actually called when the application is run, and I get error:

Unsatisfied code symbol 'rrd_clear_error'

and this symbol is exactly contained in librrd.so

Re: GCC doesn't link libraries properly

Kalin Evtimov — Mon, 04 Jul 2005 05:34:29 GMT

I got it! It was actually the option +b, which should look like +b(library/path/), but within my makefile it had not parameters, so I added them and it worked so far..