use of +b and finding dependent libs

[Vincent DiRIco]

I'm having a problem linking in IPF/PA-64 Mode. We use +b to embed a path in shared libraries. Is it possible to prevent use of embedded paths at link time to find dependent libraries?

thanks

Vinny

[Dennis Handly]

What's your linker problem?

>IPF/PA-64

What did you mean by this? You have problems with the ELF linker on both PA and IPF?

>Is it possible to prevent use of embedded paths at link time to find dependent libraries?

What did you want to use instead? -L path should work.

[Vincent DiRIco]

The dependent libs are being loaded from the +b path (the system) during link. I do specify -L path and shlibs are found there (just not the dependent libs). My goal is to have all shlibs (even dependent libs) loaded from -L path.

thanks

Vinny

[Dennis Handly]

>My goal is to have all shlibs (even dependent libs) loaded from -L path.

How do you know which path is being used?
You are using tusc? An obvious versioning difference?
Any errors you are getting?

[Vincent DiRIco]

Thanks for your time. No errors, -Wl,-t lists the full pah to shlibs opened.

thanks

Vinny

[Dennis Handly]

>No errors, -Wl,-t lists the full path to shlibs opened.

Ok, you know the magic option.
If no errors, you could ignore this.

[Vincent DiRIco]

No I need to ignore the dependent shlib on the system and use the one located at the -L path, for example here:

Loading /hp11_ia64_stage/stage/hp11_ia64/pvtshlib/libks.so:

Loading /opt/product/shlib/libezrpc.so:

libezrpc.so should have been read from "/hp11_ia64_stage/stage/hp11_ia64/pvtshlib" there is a new version staged there.

-L contains:
/hp11_ia64_stage/stage/hp11_ia64/pvtshlib

libks.so +b contains:
/opt/product/shlib

libks.so pulls in libezrpc.so

thanks

Vinny

[Dennis Handly]

>I need to ignore the dependent shlib on the system

Why? What problems can you detect?
(As far as I know, there is nothing you can do to change this, other than removing the existing shlib in the +b path.)