Still wrestling with -AA

[Bill Calver]

Hi,

I'm building a shared library which depends on (3) other shared libs that I've also built. I've linked and compiled them all with aCC using -AA. Loading the final lib fails with unsats from libCsup_v2.2. Looking at the link command in my log files I see -AA at the head of each command but I don't see -lCsup_v2 in the commands. I also don't see libCsup_v2.sl through chatr or ldd.

Should I see -lCsup_v2 on the command line when using -AA? Should I see libCsup_v2.sl from chatr and ldd? My guess is yes.

btw:
bash-2.04$ aCC -V
aCC: HP ANSI C++ B3910B A.03.70

TIA,
Bill

[Dennis Handly · Accepted solution]

No dependent shlibs are added when doing -b links. Either those libs should be automatically added to the -AA executable. Or for plugins, you need to add them. Make sure you follow the lib ordering exactly:
http://docs.hp.com/en/7762/5991-4874/distributing.htm#linking

[Bill Calver]

It should be enough to explicitly link just the final lib to Csup_v2 since it is the only one complaining about those symbols, correct?

[Dennis Handly]

>It should be enough to explicitly link just the final lib to -lCsup_v2 since it is the only one complaining about those symbols

If you say so. It is kind of hard to make a aC++ load module that doesn't depend on libCsup, so I would think all 4 need it.

Unless you know you always use all 4 together.

[Bill Calver]

Dennis,

I agree that would be a good practice but I've thought I was doing that and still run into unsats...