In linking a module on a HP-UX 11.0 system using aCC B3910B A.03.31, I have
a dynamic library that I need to add to the link step. This library does
not follow the 'standard' naming convention, LIBxxxx.SL, but rather has
a unique project related name (etiprack). I therefore cannot use the
-l or -s link options as they only work with dynamic libraries with a
standard name.

My problem is when I specify this 'non-standard' library to the linker,
I find that I have to specify the complete path (/path/etiprack) to it
or the linker won't find it. This presents a problem as this library
is now designated as 'static' in the executable attributes:

-bash-2.05b$ chatr et3_api_kak
et3_api_kak:
shared library
shared library dynamic path search:
SHLIB_PATH enabled first
embedded path disabled second Not Defined
shared library list:
dynamic /usr/lib/libCsup.2
static /afs/apd/func/et4/binhp32/etiprack

Notice etiprack is designated as 'static'. I can 'fix' this via

chatr -l /afs/apd/func/et4/binhp32/etiprack et3_api

However, I'd like to 'fix' this up front during the actual linkedit stage.
Is there someway I can link a dynamic library (e.g. etiprack) with a
non-standard name and have it designated as dynamic; i.e. without the
path having to be hard coded?